Triple
T5813223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Pacific Railroad |
E128920
|
entity |
| Predicate | openedMainLineYear |
P2467
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Western Pacific Railroad, openedMainLineYear, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedMainLineYear Context triple: [Western Pacific Railroad, openedMainLineYear, 1909]
-
A.
firstLineOpeningDate
Indicates the date on which the first line in a system, network, or service was officially opened or began operation.
-
B.
officialOpeningYear
chosen
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
C.
openingDateLine16
Indicates the date on which line 16 was officially opened or began operation.
-
D.
openedFirstLine
Indicates that one entity initiated the opening of something (e.g., a file, document, or interface) before any other entity did, being the first to perform the opening action.
-
E.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
- 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_69c0084788848190bcf71f6bc5d71597 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b56044c8190847478a342d441c2 |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021d5ecd081908a62dd66e26f8598 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.