Triple
T21551070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcombe Point |
E531761
|
entity |
| Predicate | hasGeologicalAgeRange |
P43544
|
FINISHED |
| Object | Triassic |
—
|
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: Triassic | Statement: [Orcombe Point, hasGeologicalAgeRange, Triassic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicalAgeRange Context triple: [Orcombe Point, hasGeologicalAgeRange, Triassic]
-
A.
geologicalRange
chosen
Indicates the span of geological time during which an entity (such as a taxon or formation) is known to have existed or been present.
-
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.
hasGeologicalAgeDescription
Indicates that an entity is associated with a textual description specifying its geological age or period in Earth’s history.
-
D.
geologicAgeRelativeTo
Indicates the relative chronological order between two geologic ages, specifying which one is older or younger without giving an absolute date.
-
E.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59258b88190966c18f1f519dad6 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.