Triple
T10138273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orosirian Period |
E226915
|
entity |
| Predicate | positionInPaleoproterozoic |
P88421
|
FINISHED |
| Object | third period |
—
|
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: third period | Statement: [Orosirian Period, positionInPaleoproterozoic, third period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPaleoproterozoic Context triple: [Orosirian Period, positionInPaleoproterozoic, third period]
-
A.
positionInArchean
Indicates that one entity occupies a specific spatial or stratigraphic position within the Archean eon.
-
B.
positionInGeologicTimescale
chosen
Indicates the relative placement of a time interval or event within the structured sequence of the geologic timescale.
-
C.
positionInDevonian
Indicates that one entity occupies a specific position, interval, or placement within the temporal span of the Devonian period.
-
D.
positionInSilurian
Indicates that something occupies a specific position or location within the Silurian geological period.
-
E.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
- 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_69ca8433ec308190b8b25a6fe359c34c |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cde88344a481909ee833451fab6e58 |
completed | April 2, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba4f5d88190ba68e63be10b08c7 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:06 p.m.