Triple
T26864009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Gorge |
E676414
|
entity |
| Predicate | approximateRockAge |
P52881
|
FINISHED |
| Object | 1.7 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: 1.7 billion years | Statement: [Inner Gorge, approximateRockAge, 1.7 billion years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRockAge Context triple: [Inner Gorge, approximateRockAge, 1.7 billion years]
-
A.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
B.
hasApproximateDipOfOlderRocks
Indicates that the dip (inclination) of older rock layers is approximately equal to a specified dip value or orientation.
-
C.
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.
-
D.
approximateAgeBeforePresent
chosen
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
E.
hasApproximateDipOfYoungerRocks
Indicates that the younger rock layers have an approximate dip (inclination) of a specified amount or direction relative to horizontal.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 5:27 a.m.