Triple
T11261724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shasta Route |
E266576
|
entity |
| Predicate | railwayClass |
P98797
|
FINISHED |
| Object | main line |
—
|
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: main line | Statement: [Shasta Route, railwayClass, main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayClass Context triple: [Shasta Route, railwayClass, main line]
-
A.
railroadClass
Indicates the classification or category of a railroad according to an established system (e.g., by size, revenue, or regulatory status).
-
B.
speedClassOfTrains
Indicates the classification of trains based on their operating speed or speed category.
-
C.
railwayCarriageUsedFor
Indicates that a railway carriage is employed or designated for a particular purpose, function, or type of use.
-
D.
operatedRollingStockClass
Indicates that an entity (such as a company or operator) has operated a specific class or type of rolling stock (e.g., trains or rail vehicles).
-
E.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e94c066c8190be1e032eb328e5fe |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.