Triple
T5758042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver and Rio Grande Western Railroad |
E127019
|
entity |
| Predicate | laterGauge |
P13710
|
FINISHED |
| Object | standard gauge |
—
|
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: standard gauge | Statement: [Denver and Rio Grande Western Railroad, laterGauge, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterGauge Context triple: [Denver and Rio Grande Western Railroad, laterGauge, standard gauge]
-
A.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
D.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
E.
laterStatus
chosen
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029363c988190b12f3f7b68295748 |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.