Triple
T23267966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oparara Basin |
E588205
|
entity |
| Predicate | hasFormationPeriod |
P52657
|
FINISHED |
| Object | Late Cenozoic |
—
|
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: Late Cenozoic | Statement: [Oparara Basin, hasFormationPeriod, Late Cenozoic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormationPeriod Context triple: [Oparara Basin, hasFormationPeriod, Late Cenozoic]
-
A.
mainFormationPeriod
chosen
Indicates the time span during which something was primarily formed or took shape.
-
B.
hasFormationStage
Indicates that an entity is associated with a particular stage or phase in its formation or development process.
-
C.
hasFormulationPeriod
Indicates the time span during which something is planned, designed, or developed before it is finalized or implemented.
-
D.
areFormedAt
Indicates that entities come into existence, are created, or take shape at a specific location, time, or context.
-
E.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19570fcc0819091df22140828155b |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:42 p.m.