Triple
T32266787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zintani armed coalitions |
E824307
|
entity |
| Predicate | ethnicTribalBase |
P90920
|
FINISHED |
| Object | Zintani tribes |
—
|
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: Zintani tribes | Statement: [Zintani armed coalitions, ethnicTribalBase, Zintani tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicTribalBase Context triple: [Zintani armed coalitions, ethnicTribalBase, Zintani tribes]
-
A.
ethnicOrTribalBase
chosen
Indicates that something is founded on, derived from, or primarily organized around a particular ethnic or tribal group or identity.
-
B.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
C.
numberOfTribes
Indicates the total count of distinct tribes associated with a given entity or context.
-
D.
ethnicOrTribalDesignation
Indicates that one entity is identified as having a particular ethnic or tribal affiliation or designation in relation to another entity.
-
E.
tribalCode
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 12:42 a.m.