Triple
T9700023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Guard Meritorious Unit Commendation |
E234750
|
entity |
| Predicate | deviceForAdditionalAwards |
P90760
|
FINISHED |
| Object | gold star |
—
|
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: gold star | Statement: [Coast Guard Meritorious Unit Commendation, deviceForAdditionalAwards, gold star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deviceForAdditionalAwards Context triple: [Coast Guard Meritorious Unit Commendation, deviceForAdditionalAwards, gold star]
-
A.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
B.
isSpecialAwardOf
Indicates that an award is a distinctive or exceptional honor specifically given to a particular entity (such as a person, work, or organization).
-
C.
isGameSpecificAward
Indicates that an award is specific to a particular game rather than being general or cross-game.
-
D.
awardTo
Indicates that an award, prize, or honor is given or assigned to a particular recipient.
-
E.
holderAward
Indicates that an entity has received, possesses, or is the recipient of a particular award.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d6eab0c8190abac1b009d625975 |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd081a9c5c819093439be7e802ff85 |
completed | April 1, 2026, 11:57 a.m. |
Created at: March 30, 2026, 8:18 p.m.