Triple
T2092572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Guard Unit Commendation |
E32702
|
entity |
| Predicate | scopeOfAward |
P11126
|
FINISHED |
| Object | collective unit performance |
—
|
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: collective unit performance | Statement: [Coast Guard Unit Commendation, scopeOfAward, collective unit performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfAward Context triple: [Coast Guard Unit Commendation, scopeOfAward, collective unit performance]
-
A.
awardScope
chosen
Indicates the extent, domain, or coverage that an award applies to within a given context.
-
B.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
C.
awardAspect
Indicates that one entity specifies a particular characteristic, category, or facet of an award associated with another entity.
-
D.
positionAwarded
Indicates that a specific position, role, or title has been formally granted to an entity (such as a person or organization).
-
E.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.