Triple
T20507006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bismarck Municipal Airport |
E503460
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | BIS |
—
|
NE NERFINISHED |
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: BIS | Statement: [Bismarck Municipal Airport, FAAcode, BIS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BIS Context triple: [Bismarck Municipal Airport, FAAcode, BIS]
-
A.
BIS
BIS is the commonly used abbreviation for the Basingstoke Bison, a professional ice hockey team based in Basingstoke, England.
-
B.
BIS
BIS is the Bank for International Settlements, an international financial institution that serves as a bank for central banks and fosters global monetary and financial stability.
-
C.
BIS
BIS is the National Rail station code for Bishop's Stortford railway station in Hertfordshire, England.
-
D.
BIS
BIS is the British Interplanetary Society, a long-established UK-based organization dedicated to the promotion and development of astronautics and space exploration.
-
E.
BIS
chosen
BIS is the three-letter IATA airport code for Bismarck Municipal Airport in Bismarck, North Dakota.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69dc82dd0819085d64d65a1e72c70 |
completed | April 20, 2026, 9:42 p.m. |
Created at: April 16, 2026, 11:36 a.m.