Triple
T28817448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-OAE |
E727678
|
entity |
| Predicate | geologicTimePosition |
P88421
|
FINISHED |
| Object | early Toarcian |
—
|
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: early Toarcian | Statement: [T-OAE, geologicTimePosition, early Toarcian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicTimePosition Context triple: [T-OAE, geologicTimePosition, early Toarcian]
-
A.
positionInGeologicTimescale
chosen
Indicates the relative placement of a time interval or event within the structured sequence of the geologic timescale.
-
B.
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.
-
C.
geologicTimeSubdivisionOf
Indicates that one geologic time unit is a constituent sub-division within a larger geologic time unit in the standard geologic timescale.
-
D.
geologicalPeriodRelevance
Indicates that something is relevant to, associated with, or characteristic of a particular geological period.
-
E.
geologicAgeRelativeTo
Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:33 a.m.