Triple
T29515409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bush Terminal Railroad |
E748781
|
entity |
| Predicate | servedCargoType |
P96313
|
FINISHED |
| Object | general freight |
—
|
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: general freight | Statement: [Bush Terminal Railroad, servedCargoType, general freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedCargoType Context triple: [Bush Terminal Railroad, servedCargoType, general freight]
-
A.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
B.
supportsCargoType
chosen
Indicates that one entity is capable of handling, transporting, or accommodating a specified type of cargo.
-
C.
militaryCargoOnBoard
Indicates that a vehicle, vessel, or aircraft is currently carrying military-related cargo on board.
-
D.
typicalReturnCargo
Indicates that something is the kind of cargo that is usually carried back on a return trip or journey.
-
E.
hasCargoServices
Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 28, 2026, 4:36 p.m.