Triple
T3760683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk Southern Corporation |
E82151
|
entity |
| Predicate | listedAs |
P310
|
FINISHED |
| Object | NSC |
E82151
|
NE 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: NSC | Statement: [Norfolk Southern Corporation, listedAs, NSC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NSC Context triple: [Norfolk Southern Corporation, listedAs, NSC]
-
A.
NSC
chosen
NSC is the stock ticker symbol for Norfolk Southern Corporation, a major U.S. freight railroad company.
-
B.
NSC
NSC is the commonly used abbreviation for Nashville SC, a professional soccer club based in Nashville, Tennessee, that competes in Major League Soccer.
-
C.
NSC
NSC is the commonly used abbreviation for the United Kingdom’s National Security Council, the government body responsible for coordinating national security and foreign policy.
-
D.
NSC
NSC is Pakistan’s top civilian-military forum responsible for formulating and coordinating the country’s national security and strategic policies.
-
E.
NNSC
NNSC is an international body established after the Korean War to monitor and supervise the implementation of the armistice agreement between North and South Korea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4fb0fc6248190b2f4adf3fd2d73d9 |
completed | March 14, 2026, 6:07 a.m. |
Created at: March 8, 2026, 3:35 p.m.