Triple
T22697019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palana Airport |
E561207
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | PES |
—
|
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: PES | Statement: [Palana Airport, IATACode, PES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PES Context triple: [Palana Airport, IATACode, PES]
-
A.
PES
PES is a major European political party that unites social-democratic, socialist, and labor parties from across the European Union.
-
B.
PES
PES is a Mexican political party known as Partido Encuentro Social, associated with socially conservative and evangelical Christian positions.
-
C.
PES
PES is the commonly used abbreviation for the Green Party of Switzerland, a political party focused on environmentalism and social justice.
-
D.
PES
chosen
PES is the IATA airport code for Petrozavodsk Airport in the Republic of Karelia, Russia.
-
E.
PESGB
PESGB is a professional society in the United Kingdom that brings together geoscientists and other professionals involved in petroleum exploration and related earth sciences.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789f26848190bcc5a99e3ed909e7 |
completed | April 29, 2026, 3:18 a.m. |
Created at: April 17, 2026, 3:14 p.m.