Triple
T482135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Medal |
E9190
|
entity |
| Predicate | inscriptionTheme |
P1726
|
FINISHED |
| Object | service to the security of the United States |
—
|
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: service to the security of the United States | Statement: [National Security Medal, inscriptionTheme, service to the security of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionTheme Context triple: [National Security Medal, inscriptionTheme, service to the security of the United States]
-
A.
inscription
chosen
Indicates that text has been written, carved, or engraved onto a surface or object.
-
B.
exhibitTheme
Indicates that something (such as a work, event, or presentation) presents, embodies, or is organized around a particular theme.
-
C.
campaignTheme
Indicates the central idea or message that characterizes and unifies a particular campaign.
-
D.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
E.
register
Indicates that an entity formally records or enrolls another entity or itself in an official system, list, or record.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f05a7f6c819082b4a5a3e69468a6 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.