Triple
T11321695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BOM |
E268108
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | VABB |
E268109
|
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: VABB | Statement: [BOM, ICAOCode, VABB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VABB Context triple: [BOM, ICAOCode, VABB]
-
A.
VABB
chosen
VABB is the ICAO airport code for Chhatrapati Shivaji Maharaj International Airport, the primary international airport serving Mumbai, India.
-
B.
VBB
VBB is the public transport authority and fare network that coordinates and integrates regional and urban transit services across Berlin and the surrounding Brandenburg region.
-
C.
VAB
VAB is the commonly used abbreviation for NASA’s Vehicle Assembly Building, the massive structure at Kennedy Space Center where rockets are assembled before launch.
-
D.
VABO
VABO is the ICAO airport code assigned to Vadodara Airport in Gujarat, India.
-
E.
VABP
VABP is the ICAO airport code for Raja Bhoj Airport, the primary airport serving Bhopal in the Indian state of Madhya Pradesh.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9dff37081909622623e66e17ccd |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e525ed950081908ec94cfbf8849e85 |
completed | April 19, 2026, 6:58 p.m. |
Created at: April 8, 2026, 9:32 p.m.