Triple
T21833899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrolina–Senador Nilo Coelho Airport |
E539068
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | PNZ |
—
|
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: PNZ | Statement: [Petrolina–Senador Nilo Coelho Airport, pushpinLabel, PNZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PNZ Context triple: [Petrolina–Senador Nilo Coelho Airport, pushpinLabel, PNZ]
-
A.
PNZ
chosen
PNZ is the three-letter National Rail station code for Penzance railway station in Cornwall, England.
-
B.
PZ
PZ is the Italian vehicle registration code assigned to the Province of Potenza in the Basilicata region.
-
C.
PZ
PZ is the commonly used abbreviation for Peshawar Zalmi, a professional cricket franchise that competes in the Pakistan Super League.
-
D.
PZ
PZ is the station code for Prinzregentenplatz, a Munich U-Bahn station on the city’s rapid transit network.
-
E.
PZ
PZ is the IATA airline designator assigned to LATAM Airlines Paraguay, the Paraguayan branch of the LATAM Airlines Group.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a5eeb88190b58b5b6d363cd6e3 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 16, 2026, 6:55 p.m.