Triple
T9323642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenlock |
E224331
|
entity |
| Predicate | positionInSilurian |
P87509
|
FINISHED |
| Object | second series of the Silurian |
—
|
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 series of the Silurian | Statement: [Wenlock, positionInSilurian, second series of the Silurian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSilurian Context triple: [Wenlock, positionInSilurian, second series of the Silurian]
-
A.
positionInDevonian
Indicates that one entity occupies a specific position, interval, or placement within the temporal span of the Devonian period.
-
B.
positionInJurassic
Indicates that something occupies or is assigned a specific place or role within the context of the Jurassic period.
-
C.
hasStratigraphicPosition
Indicates the relative position of one geological layer or unit within a stratigraphic sequence in relation to another.
-
D.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- F. None of above. chosen
Provenance (4 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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f5c41c81908104c5b30e14827e |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:38 p.m.