Triple
T22721978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Railroad (Missouri) |
E561885
|
entity |
| Predicate | openedSegmentDate |
P93179
|
FINISHED |
| Object | 1852 |
—
|
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: 1852 | Statement: [Pacific Railroad (Missouri), openedSegmentDate, 1852]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedSegmentDate Context triple: [Pacific Railroad (Missouri), openedSegmentDate, 1852]
-
A.
openedSegment
Indicates that one entity has initiated or created a new segment, section, or interval within another entity or process.
-
B.
openedSegmentBySegment
Indicates that something was opened gradually in distinct parts or stages, rather than all at once.
-
C.
openedFirstSegmentBetween
Indicates that one entity initiated or created the first segment in a sequence that connects it to another entity.
-
D.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
E.
lineSectionOpeningDate
chosen
Indicates the date on which a specific section of a line (e.g., a route, track, or corridor) was officially opened for use.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17926ae0c8190af8493cab6b15261 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:20 p.m.