Triple
T21747678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budweiser (U.S. Navy SEAL insignia) |
E536828
|
entity |
| Predicate | wearAuthorizedAfter |
P21364
|
FINISHED |
| Object | SEAL designation is officially awarded |
—
|
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: SEAL designation is officially awarded | Statement: [Budweiser (U.S. Navy SEAL insignia), wearAuthorizedAfter, SEAL designation is officially awarded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearAuthorizedAfter Context triple: [Budweiser (U.S. Navy SEAL insignia), wearAuthorizedAfter, SEAL designation is officially awarded]
-
A.
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.
-
B.
wearAuthorizedFor
chosen
Indicates that an entity is permitted or authorized to wear a specified item (such as clothing, equipment, or insignia).
-
C.
isWornAfter
Indicates that one item of clothing or accessory is put on later in time than another item.
-
D.
wearSchedule
Indicates a planned or prescribed pattern for when and how often something should be worn.
-
E.
wearLocation
Indicates the typical body part or location on which an item is worn.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a77e19c81909bf26f96aa41a7ce |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.