Triple
T35612100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zadran District |
E1029062
|
entity |
| Predicate | hasTribalTerritoryOf |
P178116
|
FINISHED |
| Object | Zadran tribe |
—
|
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: Zadran tribe | Statement: [Zadran District, hasTribalTerritoryOf, Zadran tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalTerritoryOf Context triple: [Zadran District, hasTribalTerritoryOf, Zadran tribe]
-
A.
tribalRegionOf
chosen
Indicates that one entity is the geographic region traditionally inhabited, controlled, or associated with a particular tribe.
-
B.
indigenousTerritoryOf
Indicates that a geographic area is traditionally inhabited, used, or claimed by a particular Indigenous people or community as their ancestral territory.
-
C.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
D.
isTribalGovernmentOf
Indicates that a tribal government holds official governing authority over a specific tribe, community, or territory.
-
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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:05 p.m.