Triple
T33549078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangal tribe |
E859285
|
entity |
| Predicate | usesDressStyle |
P42256
|
FINISHED |
| Object | traditional Pashtun attire |
—
|
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: traditional Pashtun attire | Statement: [Mangal tribe, usesDressStyle, traditional Pashtun attire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDressStyle Context triple: [Mangal tribe, usesDressStyle, traditional Pashtun attire]
-
A.
usesDressing
Indicates that one entity applies or employs a particular dressing (such as a sauce, covering, or treatment) in relation to another entity or context.
-
B.
personHasNotableStyle
Indicates that a person is recognized for having a distinctive or noteworthy style.
-
C.
fashionStyle
chosen
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
D.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
E.
wornStyle
Indicates the manner or fashion in which an item is worn or styled on an entity.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:39 a.m.