Triple
T33020081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mamund |
E844883
|
entity |
| Predicate | usesTribalCode |
P51730
|
FINISHED |
| Object | Pashtunwali |
—
|
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: Pashtunwali | Statement: [Mamund, usesTribalCode, Pashtunwali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTribalCode Context triple: [Mamund, usesTribalCode, Pashtunwali]
-
A.
tribalCode
chosen
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
-
B.
hasTribalSeal
Indicates that an entity bears, is marked with, or is officially associated with a specific tribal seal.
-
C.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
-
D.
recognizedTribeIncludes
Indicates that a formally recognized tribe encompasses or includes a particular subgroup, member, or entity within its official structure or membership.
-
E.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:23 a.m.