Triple
T27547858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazyan District |
E695411
|
entity |
| Predicate | hasMajorTribalGroup |
P34576
|
FINISHED |
| Object | Pashtun tribes |
—
|
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: Pashtun tribes | Statement: [Nazyan District, hasMajorTribalGroup, Pashtun tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorTribalGroup Context triple: [Nazyan District, hasMajorTribalGroup, Pashtun tribes]
-
A.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
B.
hasTribalMembersFrom
chosen
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
C.
hasTribalInstitution
Indicates that an entity possesses, is associated with, or hosts a tribal institution (such as a tribal government, organization, or culturally recognized tribal body).
-
D.
hasTribalMembers
Indicates that a group, organization, or entity includes individuals who are recognized as members of a specific tribe.
-
E.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: April 27, 2026, 1:33 p.m.