Triple
T36663717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serravallian |
E905200
|
entity |
| Predicate | positionInMiocene |
P88421
|
FINISHED |
| Object | second stage of Middle Miocene |
—
|
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: second stage of Middle Miocene | Statement: [Serravallian, positionInMiocene, second stage of Middle Miocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMiocene Context triple: [Serravallian, positionInMiocene, second stage of Middle Miocene]
-
A.
positionInGeologicTimescale
chosen
Indicates the relative placement of a time interval or event within the structured sequence of the geologic timescale.
-
B.
positionInJurassic
Indicates that something occupies or is assigned a specific place or role within the context of the Jurassic period.
-
C.
positionInMiddleTriassic
Indicates that something is located in time within the Middle Triassic period of the geologic timescale.
-
D.
positionInTriassic
Indicates that one entity occupies a specific position or location within the context of the Triassic period.
-
E.
positionInCambrian
Indicates the relative stratigraphic or temporal placement of something within the Cambrian 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:12 p.m.