Triple
T9502997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripuri people |
E229188
|
entity |
| Predicate | traditionalDressMale |
P15063
|
FINISHED |
| Object | rikutu |
—
|
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: rikutu | Statement: [Tripuri people, traditionalDressMale, rikutu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDressMale Context triple: [Tripuri people, traditionalDressMale, rikutu]
-
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.
nationalDress
Indicates that an item of clothing is recognized as the traditional or customary dress associated with a particular nation or culture.
-
C.
coatCharacteristic
Indicates that one entity has a particular property, feature, or quality that characterizes its outer covering or surface.
-
D.
garmentType
chosen
Indicates the specific kind or category of garment associated with an entity.
-
E.
hasTraditionalAttire
Indicates that an entity possesses or is associated with clothing that is customary or traditional within a particular culture or community.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983ea6048190a2d7924c8e6d1fbc |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.