Triple
T23521271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamale |
E574512
|
entity |
| Predicate | hasAirport |
P105
|
FINISHED |
| Object | Tamale 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: Tamale Airport | Statement: [Tamale, hasAirport, Tamale Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tamale Airport Context triple: [Tamale, hasAirport, Tamale Airport]
-
A.
Tamale Airport
chosen
Tamale Airport is a regional airport in northern Ghana that serves the city of Tamale and acts as a key air transport hub for the area.
-
B.
Sauce Viejo Airport
Sauce Viejo Airport is a regional airport serving the city of Santa Fe and its surrounding area in Argentina.
-
C.
El Caraño Airport
El Caraño Airport is the main public airport serving the city of Quibdó in Colombia’s Chocó Department.
-
D.
Los Garzones Airport
Los Garzones Airport is the main commercial airport serving the city of Montería in the Córdoba Department of Colombia.
-
E.
Guerrero Negro Airport
Guerrero Negro Airport is a small regional airport in Baja California Sur, Mexico, serving the town of Guerrero Negro and its surrounding area.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa873ad48190a86807bd4f26df82 |
completed | April 29, 2026, 6:51 a.m. |
Created at: April 17, 2026, 6:08 p.m.