Triple
T10101087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob Hope Airport |
E216200
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | BUR |
E169015
|
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: BUR | Statement: [Bob Hope Airport, IATAcode, BUR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BUR Context triple: [Bob Hope Airport, IATAcode, BUR]
-
A.
BUR
BUR is the commonly used abbreviation for the Burnaby Lakers, a Canadian box lacrosse team based in Burnaby, British Columbia.
-
B.
BUR
chosen
BUR is the three-letter IATA airport code for Hollywood Burbank Airport, a commercial airport serving the Los Angeles area in Southern California.
-
C.
Br
Br is the currency symbol used to denote the Ethiopian birr, the official monetary unit of Ethiopia.
-
D.
BOR
BOR is the commonly used abbreviation for the United States Bureau of Reclamation, a federal agency that manages water resources and hydroelectric power projects in the American West.
-
E.
BOR
BOR is the Polish Government Protection Bureau, a state security agency responsible for protecting top government officials and key state facilities.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09878f88190bcfa2c81fb10e821 |
completed | April 2, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b6d3efec8190b1432ca614aeb334 |
completed | April 5, 2026, 7:24 p.m. |
Created at: March 30, 2026, 9:02 p.m.