Triple
T28560500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuwait Emiri Guard |
E722525
|
entity |
| Predicate | uniformOf |
P18730
|
FINISHED |
| Object | distinctive ceremonial dress uniform |
—
|
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: distinctive ceremonial dress uniform | Statement: [Kuwait Emiri Guard, uniformOf, distinctive ceremonial dress uniform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniformOf Context triple: [Kuwait Emiri Guard, uniformOf, distinctive ceremonial dress uniform]
-
A.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
-
B.
areUniform
Indicates that all elements in a given set or collection share the same value, property, or characteristic.
-
C.
woreUniformOf
Indicates that one entity was dressed in or used the official uniform associated with another entity (such as an organization, group, or role).
-
D.
uniformedComponentOf
Indicates that one entity is a component or part of another entity and is required to conform to a specified uniform standard or configuration within that larger whole.
-
E.
wearsOnUniform
chosen
Indicates that an item is part of and is worn as a component of a uniform.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6505359288190b94745bff36718d5 |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:04 a.m.