Triple
T32656304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toarcis |
E834869
|
entity |
| Predicate | associatedGeologicalAge |
P1327
|
FINISHED |
| Object | Toarcian |
E199528
|
NE 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: Toarcian | Statement: [Toarcis, associatedGeologicalAge, Toarcian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGeologicalAge Context triple: [Toarcis, associatedGeologicalAge, Toarcian]
-
A.
geologicalAge
chosen
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.
geologicAgeRelativeTo
Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
-
C.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
D.
geologicalRange
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
-
E.
hasGeologicalAgeDescription
Indicates that an entity is associated with a textual description specifying its geological age or period in Earth’s history.
- F. None of above.
Provenance (4 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3492afc22481909e778082ddd6b333 |
completed | June 19, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:08 a.m.