Triple
T5929835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday Bloody Sunday |
E131906
|
entity |
| Predicate | liveShowOpenerFor |
P45486
|
FINISHED |
| Object | U2 concerts in the 1980s |
—
|
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: U2 concerts in the 1980s | Statement: [Sunday Bloody Sunday, liveShowOpenerFor, U2 concerts in the 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveShowOpenerFor Context triple: [Sunday Bloody Sunday, liveShowOpenerFor, U2 concerts in the 1980s]
-
A.
openingPerformance
chosen
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
B.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
C.
openingThemePerformer
Indicates the performer or group responsible for performing the opening theme of a work (such as a TV show, film, or game).
-
D.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
E.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
- 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_69c0085b75e88190a632f9691f9da48b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.