Triple
T1007998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian–Emperor seamount chain |
E21756
|
entity |
| Predicate | approximateOldestAge |
P16042
|
FINISHED |
| Object | about 80 million 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: about 80 million years | Statement: [Hawaiian–Emperor seamount chain, approximateOldestAge, about 80 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateOldestAge Context triple: [Hawaiian–Emperor seamount chain, approximateOldestAge, about 80 million years]
-
A.
isOldest
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
B.
estimatedAgeInMillionsOfYears
chosen
Indicates the approximate age of something expressed in units of millions of years.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
hasAge
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
E.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.