Triple
T19809597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice Presidential Service Badge |
E475906
|
entity |
| Predicate | authorizedWear |
P21364
|
FINISHED |
| Object | military 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: military uniform | Statement: [Vice Presidential Service Badge, authorizedWear, military uniform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedWear Context triple: [Vice Presidential Service Badge, authorizedWear, military uniform]
-
A.
individualWearAuthorized
Indicates that an individual is wearing an item or equipment for which they have proper authorization.
-
B.
wearAuthorizedFor
chosen
Indicates that an entity is permitted or authorized to wear a specified item (such as clothing, equipment, or insignia).
-
C.
wearAuthorizedBy
Indicates that one entity’s wearing or use of an item (such as clothing, uniform, or equipment) is permitted or approved by another entity.
-
D.
wearerEntitlement
Indicates that an entity has the right or authorization to wear a particular item (such as clothing, equipment, or an accessory).
-
E.
hasIntendedWearer
Indicates that an item is associated with the person or entity it is meant or designed to be worn by.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542ac1b48190a0cb69dbceca74da |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.