Triple
T13098533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obanliku |
E310653
|
entity |
| Predicate | hasTraditionalRulers |
P108031
|
FINISHED |
| Object | clan heads and village 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: clan heads and village chiefs | Statement: [Obanliku, hasTraditionalRulers, clan heads and village chiefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalRulers Context triple: [Obanliku, hasTraditionalRulers, clan heads and village chiefs]
-
A.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
-
B.
hasTraditionalCapital
Indicates that an entity serves or is recognized as the traditional or historical capital of another entity.
-
C.
hadPrincelyRulersIntegrated
Indicates that an entity was governed by princely rulers who were incorporated into a larger political or administrative structure.
-
D.
historicallyUnderRuleOf
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
-
E.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981500d34819097037b3c3c33627b |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:04 p.m.