Triple
T35367139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxia Planum |
E1021661
|
entity |
| Predicate | terrainAge |
P136574
|
FINISHED |
| Object | Noachian |
—
|
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: Noachian | Statement: [Oxia Planum, terrainAge, Noachian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainAge Context triple: [Oxia Planum, terrainAge, Noachian]
-
A.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
B.
surfaceAgeInterpretation
chosen
Indicates an interpretation or estimation of the age of a surface based on available geological or observational evidence.
-
C.
timeSinceMajorLandscapeFormation
Indicates the amount of time that has elapsed since a significant landscape-forming event or process last occurred.
-
D.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
E.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.