Triple
T38625230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tectonic Arena Sardona |
E936986
|
entity |
| Predicate | timeSpanOfFormation |
P116819
|
FINISHED |
| Object | over 250 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: over 250 million years | Statement: [Tectonic Arena Sardona, timeSpanOfFormation, over 250 million years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSpanOfFormation Context triple: [Tectonic Arena Sardona, timeSpanOfFormation, over 250 million years]
-
A.
monthOfFormation
Indicates the specific calendar month in which an entity (such as an organization or group) was formally established or created.
-
B.
timeSpanOfCreation
chosen
Indicates the period of time during which the creation of an entity took place.
-
C.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
D.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
E.
historicalFormationYear
Indicates the calendar year in which something (such as an organization, entity, or structure) was originally formed or established.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.