Triple
T23142870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Elizabeth Airport |
E577506
|
entity |
| Predicate | icaoCode |
P419
|
FINISHED |
| Object | FAPE |
—
|
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: FAPE | Statement: [Port Elizabeth Airport, icaoCode, FAPE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FAPE Context triple: [Port Elizabeth Airport, icaoCode, FAPE]
-
A.
FAPE
chosen
FAPE is the ICAO airport code for Chief Dawid Stuurman International Airport in Gqeberha (Port Elizabeth), South Africa.
-
B.
FAPP
FAPP is the ICAO airport code for Polokwane International Airport in Polokwane, South Africa.
-
C.
FPA
FPA is the Finnish acronym for the Social Insurance Institution of Finland, the national agency responsible for administering Finland’s social security benefits.
-
D.
FA
FA is the governing body of association football in England, responsible for overseeing the national teams, competitions, and the rules of the game within the country.
-
E.
FA
FA is the IATA airline designator assigned to FlySafair, a South African low-cost carrier.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecb72fc8190a24e8f5756217a36 |
completed | April 29, 2026, 4:53 a.m. |
Created at: April 17, 2026, 4 p.m.