Triple
T3904915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swazi people |
E90581
|
entity |
| Predicate | traditionalAttire |
P19523
|
FINISHED |
| Object | Swazi national dress |
—
|
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: Swazi national dress | Statement: [Swazi people, traditionalAttire, Swazi national dress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalAttire Context triple: [Swazi people, traditionalAttire, Swazi national dress]
-
A.
traditionalPilgrimAttire
Indicates that an entity is wearing or associated with clothing customarily worn by pilgrims in a particular cultural or religious tradition.
-
B.
nationalDress
chosen
Indicates that an item of clothing is recognized as the traditional or customary dress associated with a particular nation or culture.
-
C.
traditionalWearer
Indicates that an entity customarily wears or is characterized by wearing traditional or culturally specific clothing.
-
D.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
-
E.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.