Triple
T38264212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Grammy Awards |
E1021009
|
entity |
| Predicate | inMemoriamSegment |
P122660
|
FINISHED |
| Object | included tribute to Whitney Houston |
—
|
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: included tribute to Whitney Houston | Statement: [2013 Grammy Awards, inMemoriamSegment, included tribute to Whitney Houston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMemoriamSegment Context triple: [2013 Grammy Awards, inMemoriamSegment, included tribute to Whitney Houston]
-
A.
inMemoriamSegmentPerformer
Indicates that an entity performs or appears as a performer in an "In Memoriam" tribute segment.
-
B.
appearsInMemoryOf
Indicates that one entity is present or recalled within another entity’s memory or recollection.
-
C.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
D.
memorialEpisode
chosen
Indicates that an episode or segment is dedicated to remembering or honoring a person, event, or subject.
-
E.
memorialWork
Indicates that one entity is a commemorative work (such as a monument, plaque, or artwork) created to honor or remember 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.