Triple
T5839799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naadam |
E129561
|
entity |
| Predicate | hasTraditionalAttire |
P66644
|
FINISHED |
| Object | deel |
—
|
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: deel | Statement: [Naadam, hasTraditionalAttire, deel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalAttire Context triple: [Naadam, hasTraditionalAttire, deel]
-
A.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
-
B.
hasTraditionalDance
Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
-
C.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
D.
traditionalPilgrimAttire
Indicates that an entity is wearing or associated with clothing customarily worn by pilgrims in a particular cultural or religious tradition.
-
E.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
- F. None of above. chosen
Provenance (4 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c03c8d579081909d7b97fc9014b5d7 |
completed | March 22, 2026, 7:01 p.m. |
Created at: March 22, 2026, 3:54 p.m.