Triple
T23528324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamprusi |
E576493
|
entity |
| Predicate | hasSubChiefs |
P153120
|
FINISHED |
| Object | divisional chiefs |
—
|
LITERAL FINISHED |
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: divisional chiefs | Statement: [Mamprusi, hasSubChiefs, divisional chiefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubChiefs Context triple: [Mamprusi, hasSubChiefs, divisional chiefs]
-
A.
hasOwnChiefsDistinctFrom
Indicates that one entity has its own chiefs or leadership that are separate and distinct from those of another entity.
-
B.
hasDeputyHeads
Indicates that an entity has one or more individuals serving in subordinate leadership roles as deputy heads.
-
C.
hasCurrentChief
Indicates that one entity currently holds the position of chief or top leader of another entity.
-
D.
hasSubclan
Indicates that one clan contains or is composed of a smaller, subordinate clan within its structure.
-
E.
hasChiefTitle
Indicates that an entity holds or is associated with a specific chief-level title or designation within an organization or group.
- F. None of above. chosen
Provenance (4 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac758038819098f5f597be39274e |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:09 p.m.