Triple
T26329972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkane |
E662353
|
entity |
| Predicate | belongsToTribalArea |
P9431
|
FINISHED |
| Object | Beni Iznasen |
—
|
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: Beni Iznasen | Statement: [Berkane, belongsToTribalArea, Beni Iznasen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToTribalArea Context triple: [Berkane, belongsToTribalArea, Beni Iznasen]
-
A.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
B.
linkedToTribalEnrollment
Indicates that one entity has a direct connection or association with another entity’s tribal enrollment status or record.
-
C.
includedTribalAreas
chosen
Indicates that certain areas are designated as tribal regions and are formally included within a specified jurisdiction, boundary, or administrative scope.
-
D.
tribalRegionOf
Indicates that one entity is the geographic region traditionally inhabited, controlled, or associated with a particular tribe.
-
E.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 10:33 p.m.