Triple
T6921912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashtun belt of Balochistan |
E160205
|
entity |
| Predicate | hasTribalCulture |
P1439
|
FINISHED |
| Object | Pashtun tribal culture |
—
|
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 tribal culture | Statement: [Pashtun belt of Balochistan, hasTribalCulture, Pashtun tribal culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalCulture Context triple: [Pashtun belt of Balochistan, hasTribalCulture, Pashtun tribal culture]
-
A.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
B.
hasTribalCommunities
Indicates that an entity possesses, includes, or is associated with one or more tribal communities.
-
C.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
D.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fb8ac48190b50bbc47fad8288f |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.