Triple
T35367172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxia Planum |
E1021661
|
entity |
| Predicate | hasSurfaceAgeEstimate |
P136574
|
FINISHED |
| Object | >3.8 billion years |
—
|
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: >3.8 billion years | Statement: [Oxia Planum, hasSurfaceAgeEstimate, >3.8 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceAgeEstimate Context triple: [Oxia Planum, hasSurfaceAgeEstimate, >3.8 billion years]
-
A.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
B.
surfaceAgeInterpretation
chosen
Indicates an interpretation or estimation of the age of a surface based on available geological or observational evidence.
-
C.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
D.
estimatedAgeYears
Indicates the approximate number of years assigned as an entity’s age based on estimation rather than exact measurement.
-
E.
hasApproximateDipOfOlderRocks
Indicates that the dip (inclination) of older rock layers is approximately equal to a specified dip value or orientation.
- 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_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.