Triple
T13998605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAA |
E336764
|
entity |
| Predicate | associatedWithICAOCode |
P419
|
FINISHED |
| Object | VOMM |
E336765
|
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: VOMM | Statement: [MAA, associatedWithICAOCode, VOMM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VOMM Context triple: [MAA, associatedWithICAOCode, VOMM]
-
A.
VOMM
chosen
VOMM is the ICAO airport code for Chennai International Airport, a major aviation hub in southern India.
-
B.
VOMY
VOMY is the ICAO airport code for Mysore Airport in Mysuru, Karnataka, India.
-
C.
VOMD
VOMD is the ICAO airport code for Madurai International Airport, a major air gateway serving the city of Madurai in the Indian state of Tamil Nadu.
-
D.
Vomag
Vomag was a German vehicle manufacturer best known for producing military trucks and armored vehicles, including variants of the Panzer IV, during the World War II era.
-
E.
vamkok
Vamkok is a traditional garment worn by the Karbi people of Northeast India, reflecting their cultural identity and heritage.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb81b208190a961e49a02fa4140 |
completed | April 14, 2026, 12:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac9f1f6c8190af7ddac920661bd5 |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:19 p.m.