Triple
T36015997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suleimankhel |
E1041839
|
entity |
| Predicate | hasTribalOrganization |
P185293
|
FINISHED |
| Object | clan-based |
—
|
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: clan-based | Statement: [Suleimankhel, hasTribalOrganization, clan-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalOrganization Context triple: [Suleimankhel, hasTribalOrganization, clan-based]
-
A.
hasTribalInstitution
chosen
Indicates that an entity possesses, is associated with, or hosts a tribal institution (such as a tribal government, organization, or culturally recognized tribal body).
-
B.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
C.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
D.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
E.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:07 p.m.