Triple
T657209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Railway |
E11672
|
entity |
| Predicate | hauls |
P18005
|
FINISHED |
| Object | intermodal containers |
—
|
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: intermodal containers | Statement: [Norfolk Southern Railway, hauls, intermodal containers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hauls Context triple: [Norfolk Southern Railway, hauls, intermodal containers]
-
A.
catches
Indicates that one entity successfully seizes, intercepts, or takes hold of another entity, often stopping its motion or preventing its escape.
-
B.
seal
Indicates that an agent closes or fastens something so that it is securely shut and often airtight or watertight.
-
C.
has
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
D.
bay
Indicates that one entity howls or barks loudly, often repeatedly, typically in reaction to something such as prey, the moon, or a disturbance.
-
E.
reserves
Indicates that an entity has arranged in advance to hold or secure something for future use or access.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fa55e048190bd9913c6c31772d0 |
completed | March 1, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69a49d121cec81909986c91291bb4ca8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49ee356c0819085e2e82831cf1360 |
completed | March 1, 2026, 8:17 p.m. |
Created at: March 1, 2026, 7:36 p.m.