Triple
T27024650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subcommission on Silurian Stratigraphy |
E680751
|
entity |
| Predicate | timeIntervalEndDefined |
P162500
|
FINISHED |
| Object | top of Silurian 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: top of Silurian Period | Statement: [Subcommission on Silurian Stratigraphy, timeIntervalEndDefined, top of Silurian Period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeIntervalEndDefined Context triple: [Subcommission on Silurian Stratigraphy, timeIntervalEndDefined, top of Silurian Period]
-
A.
timeIntervalStartDefined
Indicates that the starting point of a time interval has been explicitly specified or defined.
-
B.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
hasTemporalEnd
Indicates that an event, state, or process concludes or terminates at a specific point or interval in time.
-
D.
endAt
Indicates that an event, process, or state concludes or terminates at a specified time, location, or condition.
-
E.
eventEndTime
Indicates the specific time at which an event concludes or is considered finished.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 7:10 a.m.