Triple
T22983528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamnagar Airport |
E571535
|
entity |
| Predicate | ICAO code |
P419
|
FINISHED |
| Object | VAJM |
—
|
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: VAJM | Statement: [Jamnagar Airport, ICAO code, VAJM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VAJM Context triple: [Jamnagar Airport, ICAO code, VAJM]
-
A.
VAJM
chosen
VAJM is the ICAO airport code for Jamnagar Airport in Jamnagar, Gujarat, India.
-
B.
VAJA
VAJA is the commonly used acronym for Iran’s Ministry of Intelligence, the country’s primary intelligence and security agency.
-
C.
VJ
VJ is the abbreviation for the Yugoslav Army, the armed forces of the former Federal Republic of Yugoslavia active during the 1990s and early 2000s.
-
D.
VJRA
VJRA is a U.S. federal law that established judicial review of veterans’ benefits decisions, creating a specialized court system to handle appeals from the Department of Veterans Affairs.
-
E.
VAJB
VAJB is the ICAO airport code assigned to Dumna Airport, which serves the city of Jabalpur 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 (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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829775e881909c5d6d35d3fd57f7 |
completed | April 29, 2026, 4:01 a.m. |
Created at: April 17, 2026, 3:49 p.m.