Triple
T2092545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Valorous Unit Award |
E32701
|
entity |
| Predicate | wearAuthorizedBy |
P35896
|
FINISHED |
| Object | Army uniform regulations |
—
|
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: Army uniform regulations | Statement: [Army Valorous Unit Award, wearAuthorizedBy, Army uniform regulations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearAuthorizedBy Context triple: [Army Valorous Unit Award, wearAuthorizedBy, Army uniform regulations]
-
A.
wearAuthorizedFor
Indicates that an entity is permitted or authorized to wear a specified item (such as clothing, equipment, or insignia).
-
B.
individualWearAuthorized
Indicates that an individual is wearing an item or equipment for which they have proper authorization.
-
C.
wearLocation
Indicates the typical body part or location on which an item is worn.
-
D.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
E.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abba2e65b48190bb19cfc4b0f8c462 |
completed | March 7, 2026, 5:39 a.m. |
Created at: March 4, 2026, 7:43 p.m.