Triple
T34521469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Service Ribbon |
E886289
|
entity |
| Predicate | canHaveMultipleAwards |
P3161
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Arctic Service Ribbon, canHaveMultipleAwards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canHaveMultipleAwards Context triple: [Arctic Service Ribbon, canHaveMultipleAwards, yes]
-
A.
hasMultipleAwardsPossible
Indicates that an entity is eligible to receive or be associated with more than one award.
-
B.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
C.
canBeAwardedMultipleTimes
chosen
Indicates that the associated award, honor, or recognition may be granted to the same recipient on more than one occasion.
-
D.
hasSeparateAwardFor
Indicates that there exists a distinct, dedicated award specifically recognizing the related entity, separate from other general or combined awards.
-
E.
mayBeAwardedWith
Indicates that an entity has the potential or eligibility to receive a particular award or distinction.
- 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_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.