Triple
T20414870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbria International Airport |
E500681
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | PEG |
—
|
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: PEG | Statement: [Umbria International Airport, IATAcode, PEG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEG Context triple: [Umbria International Airport, IATAcode, PEG]
-
A.
PEG
PEG is a German vehicle registration code assigned to the Bayreuth district region.
-
B.
PEG
PEG is the stock ticker symbol for Public Service Enterprise Group, a major U.S. energy company primarily involved in regulated electric and gas utility operations and power generation.
-
C.
PEG
chosen
PEG is the IATA airport code for Perugia San Francesco d’Assisi – Umbria International Airport in central Italy.
-
D.
PDG
PDG is the IATA airport code for Minangkabau International Airport serving Padang in West Sumatra, Indonesia.
-
E.
PDG
PDG is the abbreviation for the Parliament of the German-speaking Community in Belgium, the legislative body representing the country’s German-speaking minority.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a437eec8190a20c89a236dd5bc0 |
completed | April 20, 2026, 7:10 p.m. |
Created at: April 16, 2026, 11:30 a.m.