Triple
T31798840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Base Tamale |
E811669
|
entity |
| Predicate | isMilitarySideOf |
P110549
|
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: [Air Force Base Tamale, isMilitarySideOf, Tamale Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitarySideOf Context triple: [Air Force Base Tamale, isMilitarySideOf, Tamale Airport]
-
A.
isUnifiedMilitaryOf
Indicates that an entity serves as the single, consolidated military force representing or defending another entity (such as a state, alliance, or organization).
-
B.
forzaBelligerante
Indicates a party’s status or role as a belligerent force engaged in a conflict or war.
-
C.
conflictSide
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
D.
isMilitaryAssetOf
chosen
Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
-
E.
stateOfForces
Indicates the condition, disposition, or readiness level of military or organizational forces at a given time.
- F. None of above.
Provenance (3 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:41 p.m.