Triple
T33272576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGT & GCC |
E851812
|
entity |
| Predicate | associatedDressCode |
P2738
|
FINISHED |
| Object | modest Islamic attire |
—
|
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: modest Islamic attire | Statement: [MGT & GCC, associatedDressCode, modest Islamic attire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDressCode Context triple: [MGT & GCC, associatedDressCode, modest Islamic attire]
-
A.
hasDressCode
chosen
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
B.
entranceAttire
Indicates the required or appropriate clothing or dress code for entering a particular place or event.
-
C.
usesDressing
Indicates that one entity applies or employs a particular dressing (such as a sauce, covering, or treatment) in relation to another entity or context.
-
D.
usualAttire
Indicates the type of clothing an entity typically wears in ordinary or characteristic situations.
-
E.
typicallyWornWith
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:32 a.m.