Triple
T24459437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Llewellyn Rhys Prize |
E616775
|
entity |
| Predicate | namedAfterDeathContext |
P84617
|
FINISHED |
| Object | killed in action in World War II |
—
|
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: killed in action in World War II | Statement: [John Llewellyn Rhys Prize, namedAfterDeathContext, killed in action in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterDeathContext Context triple: [John Llewellyn Rhys Prize, namedAfterDeathContext, killed in action in World War II]
-
A.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
B.
completionAfterDeathOf
Indicates that one event, process, or work is completed only after the death of a specified person.
-
C.
namedAfterCauseOfDeath
chosen
Indicates that an entity is named after the cause of death of a person or organism.
-
D.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
E.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c8d854819091f1d92eef02b1b1 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.