Triple
T25916786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Last Time |
E653057
|
entity |
| Predicate | usedAsTribute |
P113791
|
FINISHED |
| Object | Manchester Arena bombing victims |
—
|
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: Manchester Arena bombing victims | Statement: [One Last Time, usedAsTribute, Manchester Arena bombing victims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTribute Context triple: [One Last Time, usedAsTribute, Manchester Arena bombing victims]
-
A.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
B.
subjectOfTribute
chosen
Indicates that one entity is the target or honoree of a tribute, such as a payment, offering, or act of respect made by another entity.
-
C.
usedAsDedicationFor
Indicates that something (such as a work, object, or act) is dedicated in honor of, or specifically intended for, another entity.
-
D.
appearsInMemoryOf
Indicates that one entity is present or recalled within another entity’s memory or recollection.
-
E.
sacrificedTo
Indicates that one entity is offered or given up as a sacrifice in honor of, or to appease, 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 8:31 a.m.