Triple
T18663990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHWW |
E456277
|
entity |
| Predicate | associatedIataCode |
P2569
|
FINISHED |
| Object | VVO |
—
|
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: VVO | Statement: [UHWW, associatedIataCode, VVO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VVO Context triple: [UHWW, associatedIataCode, VVO]
-
A.
VVO
chosen
VVO is the three-letter IATA airport code for Vladivostok International Airport in Russia.
-
B.
VVI
VVI is the IATA airport code for Viru Viru International Airport, the main international gateway serving Santa Cruz de la Sierra, Bolivia.
-
C.
VOH
VOH is the vehicle registration code used on license plates for the district of Neustadt an der Waldnaab in Bavaria, Germany.
-
D.
VELO
VELO is the high-precision vertex detector of the LHCb experiment at CERN, designed to measure particle trajectories very close to the proton–proton collision point.
-
E.
VOG
VOG is the IATA airport code for Volgograd International Airport, a regional air transport hub serving the city of Volgograd in Russia.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508d2d588190a468bd7b205d2057 |
completed | April 19, 2026, 10 p.m. |
Created at: April 10, 2026, 11:48 a.m.