Triple
T28642105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coast Guard Meritorious Service Medal |
E724953
|
entity |
| Predicate | combatDistinction |
P81668
|
FINISHED |
| Object | no combat "V" device |
—
|
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: no combat "V" device | Statement: [Coast Guard Meritorious Service Medal, combatDistinction, no combat "V" device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatDistinction Context triple: [Coast Guard Meritorious Service Medal, combatDistinction, no combat "V" device]
-
A.
combatDistinctionDevice
chosen
Indicates a special recognition or device awarded to denote distinguished performance or merit in combat-related actions or operations.
-
B.
combatRecord
Indicates that an entity maintains a documented history of its participation in combat or battles.
-
C.
combatIndicator
Indicates that an entity is involved in, associated with, or signaling the occurrence of combat or hostile activity.
-
D.
combatView
Indicates a perspective or representation of entities engaged in combat or battle-related interaction.
-
E.
battleCharacteristic
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:45 a.m.