Triple
T34521462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Service Ribbon |
E886289
|
entity |
| Predicate | isDecorationFor |
P8752
|
FINISHED |
| Object | meritorious service in Arctic conditions |
—
|
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: meritorious service in Arctic conditions | Statement: [Arctic Service Ribbon, isDecorationFor, meritorious service in Arctic conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDecorationFor Context triple: [Arctic Service Ribbon, isDecorationFor, meritorious service in Arctic conditions]
-
A.
containsDecorationFrom
Indicates that one entity includes or incorporates a decorative element that originates from another entity.
-
B.
isStateDecoration
Indicates that an item is an official decoration or honor conferred by a state or government authority.
-
C.
hasDecor
Indicates that one entity possesses, features, or is adorned with a particular decorative element or style.
-
D.
typeOfDecoration
Indicates the specific kind or style of decoration associated with an entity or applied in a given context.
-
E.
isWearableDecoration
chosen
Indicates that one entity serves as a decorative item intended to be worn on the body by another entity.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb317f0819089112d0a08a64c51 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.