Triple
T18998772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venice Marco Polo Airport |
E464889
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | LIPZ |
—
|
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: LIPZ | Statement: [Venice Marco Polo Airport, ICAOCode, LIPZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LIPZ Context triple: [Venice Marco Polo Airport, ICAOCode, LIPZ]
-
A.
LIPZ
chosen
LIPZ is the ICAO airport code for Venice Marco Polo Airport, the main international airport serving Venice, Italy.
-
B.
LIP
LIP is the vehicle registration code for the town of Blomberg in the Lippe district of North Rhine-Westphalia, Germany.
-
C.
LIP
LIP is the vehicle registration code for the district of Lippe in the German state of North Rhine-Westphalia.
-
D.
LIPK
LIPK is the ICAO airport code for Forlì International Airport in Forlì, Italy.
-
E.
LIPY
LIPY is the ICAO airport code for Ancona Airport, a regional airport serving the city of Ancona and the Marche region in Italy.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6838f4481909b265e29964b0dca |
completed | April 20, 2026, 7:32 a.m. |
Created at: April 10, 2026, 12:01 p.m.