Triple
T657231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Railway |
E11672
|
entity |
| Predicate | hasSubsidiaryType |
P3504
|
FINISHED |
| Object | short line railroads |
—
|
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: short line railroads | Statement: [Norfolk Southern Railway, hasSubsidiaryType, short line railroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryType Context triple: [Norfolk Southern Railway, hasSubsidiaryType, short line railroads]
-
A.
hasSubsidiaryTitle
Indicates that an entity has an additional or secondary title formally associated with its main title.
-
B.
hasSubsidiaryPyramid
Indicates that one entity is a subsidiary or subordinate component within a larger, pyramid-structured entity.
-
C.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
D.
hasTypeOfOrganization
chosen
Indicates that an entity is classified as belonging to a particular type or category of organization.
-
E.
notableSubsidiary
Indicates that one entity is a subsidiary of another and is particularly significant or prominent among that parent’s subsidiaries.
- 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_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. |
Created at: March 1, 2026, 7:36 p.m.