Triple
T22161652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Northern Railway |
E547684
|
entity |
| Predicate | usedPassengerService |
P4906
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sacramento Northern Railway, usedPassengerService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPassengerService Context triple: [Sacramento Northern Railway, usedPassengerService, yes]
-
A.
openedAsPassengerService
Indicates that a transportation facility or route began operating specifically for carrying passengers.
-
B.
formerPassengerService
chosen
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
C.
isInPassengerService
Indicates that an entity (such as a vehicle, vessel, or aircraft) is currently being used to carry passengers as part of regular service.
-
D.
hasPassengerAirlineService
Indicates that a location or facility is served by scheduled passenger airline flights.
-
E.
hasPassengerUsageCategory
Indicates the classification of how a passenger-related resource or service is used (e.g., its usage type or category for passengers).
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2d8064819094d27ef9f15c6a1f |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.