Triple
T1267721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expert Infantryman Badge |
E15638
|
entity |
| Predicate | wearerEntitlement |
P28027
|
FINISHED |
| Object | permanent award once earned |
—
|
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: permanent award once earned | Statement: [Expert Infantryman Badge, wearerEntitlement, permanent award once earned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerEntitlement Context triple: [Expert Infantryman Badge, wearerEntitlement, permanent award once earned]
-
A.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
B.
individualWearAuthorized
Indicates that an individual is wearing an item or equipment for which they have proper authorization.
-
C.
wearAuthorizedFor
Indicates that an entity is permitted or authorized to wear a specified item (such as clothing, equipment, or insignia).
-
D.
wearerDevice
Indicates that a device is worn or carried by a particular entity (the wearer).
-
E.
individualWear
Indicates that an individual is wearing or has clothing or an accessory on their body.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0396e048190b4e2d7aab19268b3 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:50 p.m.