Triple
T27024649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subcommission on Silurian Stratigraphy |
E680751
|
entity |
| Predicate | timeIntervalStartDefined |
P162030
|
FINISHED |
| Object | base 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: base of Silurian Period | Statement: [Subcommission on Silurian Stratigraphy, timeIntervalStartDefined, base of Silurian Period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeIntervalStartDefined Context triple: [Subcommission on Silurian Stratigraphy, timeIntervalStartDefined, base of Silurian Period]
-
A.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
B.
requiresStartTime
Indicates that an entity cannot be valid, initiated, or executed unless a specific start time has been provided or is in effect.
-
C.
timePeriodAnalyzedStart
Indicates the starting point in time from which a given period is examined or analyzed.
-
D.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
E.
timeIntervalLength
Indicates the duration or length of a specified time interval.
- 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_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 7:10 a.m.