Triple
T26235805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commendation for Brave Conduct |
E656160
|
entity |
| Predicate | hasMultipleAwardsPossible |
P169544
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Commendation for Brave Conduct, hasMultipleAwardsPossible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleAwardsPossible Context triple: [Commendation for Brave Conduct, hasMultipleAwardsPossible, true]
-
A.
hasMultipleAwardsIndicatedBy
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
B.
mayBeAwardedWith
Indicates that an entity has the potential or eligibility to receive a particular award or distinction.
-
C.
hasAwardConnection
Indicates a relationship where an entity is connected to an award, such as by receiving, being nominated for, or otherwise associated with that award.
-
D.
hasAwardField
Indicates that an entity’s award is associated with or categorized under a particular field or domain.
-
E.
numberOfAwards
Indicates the total count of awards that have been received by an entity.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 26, 2026, 9:01 p.m.