Triple
T3760685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Corporation |
E82151
|
entity |
| Predicate | operatesInSubsector |
P2193
|
FINISHED |
| Object | 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: railroads | Statement: [Norfolk Southern Corporation, operatesInSubsector, railroads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInSubsector Context triple: [Norfolk Southern Corporation, operatesInSubsector, railroads]
-
A.
operatesInSegment
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
-
B.
alsoOperatesIn
Indicates that an entity, in addition to its primary location or domain, conducts operations or activities in another specified place or context.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
E.
sectorServed
chosen
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbc553a08190ba361675901496ed |
completed | March 8, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.