Triple
T19114464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excellence-in-Competition Badge |
E467870
|
entity |
| Predicate | regulatesWearOn |
P130658
|
FINISHED |
| Object | U.S. military uniforms |
—
|
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: U.S. military uniforms | Statement: [Excellence-in-Competition Badge, regulatesWearOn, U.S. military uniforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesWearOn Context triple: [Excellence-in-Competition Badge, regulatesWearOn, U.S. military uniforms]
-
A.
wearingRegulatedBy
chosen
Indicates that the act of wearing something is governed, constrained, or directed by a rule, regulation, or authority.
-
B.
typeOfWear
Indicates the specific manner or style in which something is worn or used as clothing or adornment.
-
C.
orderOfWear
Indicates the relative sequence in which items are intended to be worn, specifying which item is put on before or after another.
-
D.
wornUntil
Indicates that an item of clothing or wearable object was used or worn continuously up to a specific time or event.
-
E.
wearRegulation
Indicates that an entity is subject to and follows specific rules or standards governing what it wears.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39617408190b5134918f54f9c52 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.