Triple
T31170324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Give Up the Ghost |
E794585
|
entity |
| Predicate | firstPerformedLiveBy |
P85365
|
FINISHED |
| Object | Radiohead |
E43669
|
NE 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: Radiohead | Statement: [Give Up the Ghost, firstPerformedLiveBy, Radiohead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformedLiveBy Context triple: [Give Up the Ghost, firstPerformedLiveBy, Radiohead]
-
A.
firstPerformedLive
chosen
Indicates that an entity (such as a work or piece) was performed live for the first time by a particular agent, at a specific event, place, or date.
-
B.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
C.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
D.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
E.
hasNotableLivePerformancesWith
Indicates that two entities have shared notable live performances together, such as concerts, shows, or events where they appeared or performed jointly.
- F. None of above.
Provenance (4 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e1545108190a3a47039c9cb636f |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:07 p.m.