Triple
T31907376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dishdasha |
E814589
|
entity |
| Predicate | typicalWearerRegion |
P15483
|
FINISHED |
| Object | Iraq |
E6006
|
NE 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: Iraq | Statement: [Dishdasha, typicalWearerRegion, Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWearerRegion Context triple: [Dishdasha, typicalWearerRegion, Iraq]
-
A.
typicalBlendPartnerRegion
Indicates that one region is commonly used as a blending partner with another region in typical combinations or mixtures.
-
B.
usesRegionType
Indicates that one entity operates within, is configured for, or otherwise makes use of a specified type of region.
-
C.
usedForPeopleOfRegion
Indicates that something is intended to be used by, or is suitable for, people from a specific geographic region.
-
D.
hasTypicalUsageRegion
chosen
Indicates that something is most commonly or characteristically used within a particular geographic region.
-
E.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
- F. None of above.
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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e7fd7854c81908ae406f984d9940f |
completed | June 14, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, midnight