Triple
T34618792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Funhouse |
E888939
|
entity |
| Predicate | containsHomageTo |
P8708
|
FINISHED |
| Object | Psycho |
—
|
NE NERFINISHED |
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: Psycho | Statement: [The Funhouse, containsHomageTo, Psycho]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHomageTo Context triple: [The Funhouse, containsHomageTo, Psycho]
-
A.
paysHomageTo
chosen
Indicates that one entity formally shows respect, reverence, or honor toward another, often acknowledging its superiority, influence, or authority.
-
B.
hasPartInHisHonor
Indicates that something includes or contains a part, section, or component that is dedicated or named in honor of a particular person.
-
C.
isGivenInHonorOf
Indicates that something (such as an award, gift, or event) is presented or dedicated as a mark of respect or recognition for a particular person or entity.
-
D.
isTributeRecordingOf
Indicates that one recording is a tribute performance or version created in honor of another original recording.
-
E.
hasTribute
Indicates that one entity pays or owes tribute to another entity, typically as a sign of submission, allegiance, or obligation.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: May 1, 2026, 2:03 a.m.