Triple
T21417890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wa |
E528353
|
entity |
| Predicate | hasTransportInfrastructure |
P2560
|
FINISHED |
| Object | Wa Airport |
—
|
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: Wa Airport | Statement: [Wa, hasTransportInfrastructure, Wa Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wa Airport Context triple: [Wa, hasTransportInfrastructure, Wa Airport]
-
A.
Wa Airport
chosen
Wa Airport is a regional public airport serving the city of Wa and its surrounding areas in the Upper West Region of Ghana.
-
B.
Ho Airport
Ho Airport is a domestic airport serving the city of Ho in Ghana’s Volta Region.
-
C.
Homiel Airport
Homiel Airport is a regional public airport serving the city of Gomel in southeastern Belarus, handling domestic and limited international flights.
-
D.
HIN Airport
HIN Airport is the IATA-designated regional airport serving Sacheon and the nearby city of Jinju in South Gyeongsang Province, South Korea.
-
E.
Mwanza Airport
Mwanza Airport is a regional airport in Mwanza, Tanzania, serving as a key hub for domestic flights and connections around Lake Victoria.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee62d29f948190b820c92014d1c53a |
completed | April 26, 2026, 7:09 p.m. |
Created at: April 16, 2026, 5:46 p.m.