Triple
T24649014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenata tribal confederations of North Africa |
E610194
|
entity |
| Predicate | includedTribe |
P32607
|
FINISHED |
| Object | Miknasa |
—
|
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: Miknasa | Statement: [Zenata tribal confederations of North Africa, includedTribe, Miknasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedTribe Context triple: [Zenata tribal confederations of North Africa, includedTribe, Miknasa]
-
A.
includesTribe
chosen
Indicates that one entity contains, encompasses, or has within it a particular tribe as a member or component.
-
B.
includedTribalType
Indicates that one entity is classified as belonging to, or being part of, a specified tribal category or type.
-
C.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
-
D.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
E.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 2:33 a.m.