Triple
T10690158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgil I. Grissom Municipal Airport |
E251988
|
entity |
| Predicate | hasFAAcode |
P420
|
FINISHED |
| Object | BFR |
E879245
|
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: BFR | Statement: [Virgil I. Grissom Municipal Airport, hasFAAcode, BFR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BFR Context triple: [Virgil I. Grissom Municipal Airport, hasFAAcode, BFR]
-
A.
BFR
chosen
BFR is the IATA airport code for Virgil I. Grissom Municipal Airport in Bedford, Indiana, United States.
-
B.
BFR
BFR, now known as SpaceX's Starship launch system, is a fully reusable, next-generation spacecraft and rocket designed for missions to Earth orbit, the Moon, Mars, and beyond.
-
C.
BFR
BFR is the National Rail station code for Blackfriars railway station in central London.
-
D.
BFR
BFR is the common abbreviation for Botafogo de Futebol e Regatas, a traditional Brazilian football club based in Rio de Janeiro.
-
E.
ITS (Interplanetary Transport System)
ITS (Interplanetary Transport System) was SpaceX’s original conceptual architecture for a fully reusable, super-heavy launch and spacecraft system intended to enable large-scale human colonization of Mars.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd1c0f0081908a6869ee756ec789 |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d998cfeb748190bfff06534d83cf97 |
completed | April 11, 2026, 12:41 a.m. |
Created at: April 8, 2026, 9:11 p.m.