Triple
T17179295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HiRISE |
E416938
|
entity |
| Predicate | typicalImageLength |
P18065
|
FINISHED |
| Object | up to tens of kilometers |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: up to tens of kilometers | Statement: [HiRISE, typicalImageLength, up to tens of kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImageLength Context triple: [HiRISE, typicalImageLength, up to tens of kilometers]
-
A.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
B.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
C.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
D.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0f9a288190b0ddfb673bd8e84b |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.