Triple
T29211356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhoti |
E740552
|
entity |
| Predicate | formalWearIn |
P6085
|
FINISHED |
| Object | many Indian states |
—
|
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: many Indian states | Statement: [Dhoti, formalWearIn, many Indian states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalWearIn Context triple: [Dhoti, formalWearIn, many Indian states]
-
A.
formalSetting
Indicates that the associated interaction, event, or context occurs in a formal or official setting governed by explicit social or institutional norms.
-
B.
usualAttire
Indicates the type of clothing an entity typically wears in ordinary or characteristic situations.
-
C.
wearingForm
Indicates that one entity is dressed in or has on a particular form of clothing, outfit, or wearable item.
-
D.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
E.
ceremonialDressFeature
chosen
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 12:11 p.m.