Triple
T13460870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shalwar kameez |
E311358
|
entity |
| Predicate | typicalFitOfShalwar |
P86094
|
FINISHED |
| Object | loose |
—
|
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: loose | Statement: [shalwar kameez, typicalFitOfShalwar, loose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFitOfShalwar Context triple: [shalwar kameez, typicalFitOfShalwar, loose]
-
A.
typicalFit
chosen
Indicates that one entity is a usual, expected, or characteristic match or correspondence for another in a given context.
-
B.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
C.
shirtNumberType
Indicates the type or category of a shirt number assigned to an entity (for example, a player’s jersey number type).
-
D.
hasTypicalSleeveStyle
Indicates the usual or characteristic sleeve design associated with an item, such as a garment or uniform.
-
E.
traditionalDressVariant
Indicates that one traditional dress is a variant or localized form of another traditional dress within the same broader cultural or stylistic tradition.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0c177081909178dec61b09c278 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.