Triple
T24818250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero of the Russian Federation |
E620983
|
entity |
| Predicate | multipleAwardsInsignia |
P23624
|
FINISHED |
| Object | additional Gold Star medals |
—
|
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: additional Gold Star medals | Statement: [Hero of the Russian Federation, multipleAwardsInsignia, additional Gold Star medals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multipleAwardsInsignia Context triple: [Hero of the Russian Federation, multipleAwardsInsignia, additional Gold Star medals]
-
A.
hasMultipleAwardsIndicatedBy
chosen
Indicates that an entity is recognized as having received multiple awards, as evidenced or signaled by a specified source or indicator.
-
B.
numberOfAwards
Indicates the total count of awards that have been received by an entity.
-
C.
alsoAwardedIn
Indicates that the same award or recognition was given in an additional time, place, or context beyond the primary one.
-
D.
hasAwardStatueName
Indicates that an entity has been given or is associated with an award whose statue (trophy) has the specified name.
-
E.
awardsAre
Indicates that one entity confers or grants awards or honors to 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:03 a.m.