Triple
T27793602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ga Traditional Council |
E701146
|
entity |
| Predicate | capitalOfTraditionalArea |
P85786
|
FINISHED |
| Object | Accra |
—
|
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: Accra | Statement: [Ga Traditional Council, capitalOfTraditionalArea, Accra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfTraditionalArea Context triple: [Ga Traditional Council, capitalOfTraditionalArea, Accra]
-
A.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
B.
capitalOfReferencedRegion
chosen
Indicates that one entity serves as the capital city or administrative center of the region referenced by another entity.
-
C.
capitalSettlementOfRegion
Indicates that a settlement serves as the administrative or political capital of a specified region.
-
D.
capitalOfSubdivision
Indicates that a place serves as the administrative capital of a specified subnational division (such as a state, province, or region).
-
E.
capitalLocatedInRegion
Indicates that a capital city is geographically situated within a specific region.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 5:29 p.m.