Triple
T7308563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekhela chador |
E168036
|
entity |
| Predicate | hasComponentShape |
P76214
|
FINISHED |
| Object | tubular lower garment |
—
|
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: tubular lower garment | Statement: [Mekhela chador, hasComponentShape, tubular lower garment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentShape Context triple: [Mekhela chador, hasComponentShape, tubular lower garment]
-
A.
hasCommonShape
Indicates that two or more entities share the same or a very similar geometric or visual shape.
-
B.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
-
C.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
D.
hasComponentCount
Indicates that an entity is associated with a specific number of components it contains or comprises.
-
E.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebda7b748190a230a22ecea79342 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:01 p.m.