Triple
T22161651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Northern Railway |
E547684
|
entity |
| Predicate | usedFreightService |
P11980
|
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, usedFreightService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFreightService Context triple: [Sacramento Northern Railway, usedFreightService, yes]
-
A.
usedForService
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
-
B.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
C.
hasCargoServices
chosen
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
-
D.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
E.
hasFreightHistory
Indicates that an entity has a recorded history of freight-related activities, such as shipments or cargo movements, associated with it.
- 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.