Triple
T11550950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Bend International Airport |
E273887
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | SBN |
E932701
|
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: SBN | Statement: [South Bend International Airport, FAA LID, SBN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SBN Context triple: [South Bend International Airport, FAA LID, SBN]
-
A.
SBN
chosen
SBN is the IATA airport code for South Bend International Airport, a commercial airport serving South Bend, Indiana, and the surrounding region.
-
B.
SNB
SNB is the U.S. Navy’s military transport and trainer variant of the Beechcraft Model 18 aircraft.
-
C.
SNB
SNB is the abbreviation for the Schweizerische Nordwestbahn, a former Swiss railway company that operated in the northwestern region of Switzerland.
-
D.
SNB
SNB is the central bank of Switzerland responsible for the country’s monetary policy and the stability of the Swiss financial system.
-
E.
SSBN
SSBN is a naval hull classification symbol denoting nuclear-powered ballistic missile submarines designed primarily for strategic nuclear deterrence.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a83f1e88190aabf11a4c8a6c9e5 |
completed | April 10, 2026, 5:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e71392d0388190971bab8906e5e6df |
completed | April 21, 2026, 6:05 a.m. |
Created at: April 8, 2026, 9:37 p.m.