Triple
T5682222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Lifesaving Medal |
E125224
|
entity |
| Predicate | serviceBranchUsage |
P2099
|
FINISHED |
| Object | United States Coast Guard personnel |
—
|
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: United States Coast Guard personnel | Statement: [Silver Lifesaving Medal, serviceBranchUsage, United States Coast Guard personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceBranchUsage Context triple: [Silver Lifesaving Medal, serviceBranchUsage, United States Coast Guard personnel]
-
A.
serviceBranch
chosen
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
serviceBranchSpecific
Indicates that something is restricted or tailored to a particular branch of service rather than being common across all branches.
-
C.
platformUsage
Indicates how an entity uses, engages with, or relies on a particular platform for its activities or services.
-
D.
serviceFrequencyContext
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
-
E.
serviceUseCase
Indicates that an entity is used as a service to fulfill or support a particular use case or functional 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.