Triple
T3862708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distinguished Conduct Medal |
E90175
|
entity |
| Predicate | claspPolicy |
P52412
|
FINISHED |
| Object | clasps awarded for subsequent acts of bravery |
—
|
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: clasps awarded for subsequent acts of bravery | Statement: [Distinguished Conduct Medal, claspPolicy, clasps awarded for subsequent acts of bravery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claspPolicy Context triple: [Distinguished Conduct Medal, claspPolicy, clasps awarded for subsequent acts of bravery]
-
A.
declaredPolicy
Indicates that an entity has formally stated or announced a specific policy or course of action.
-
B.
decisionPublicationPolicy
Indicates the policy or rules governing how decisions are made public or communicated.
-
C.
ordinationPolicy
Indicates the rules or criteria governing how entities are ordered, ranked, or arranged relative to one another.
-
D.
eraPolicy
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
E.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec2417648190ad010189d304d119 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:19 p.m.