Triple
T7606470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Commendation Medal |
E180116
|
entity |
| Predicate | deviceAuthorized |
P77737
|
FINISHED |
| Object | “V” device for valor |
—
|
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: “V” device for valor | Statement: [Army Commendation Medal, deviceAuthorized, “V” device for valor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviceAuthorized Context triple: [Army Commendation Medal, deviceAuthorized, “V” device for valor]
-
A.
individualWearAuthorized
Indicates that an individual is wearing an item or equipment for which they have proper authorization.
-
B.
usedToAuthorize
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
hasAlterEgoDevice
Indicates that an entity possesses or is associated with a device specifically used to enable, support, or manifest its alter ego.
-
E.
announcedWithDevice
Indicates that an announcement or communication was made using a specific device as the medium or tool.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fe10408190b1c12bb8f911cea8 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:54 p.m.