Triple
T5081442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnout |
E114517
|
entity |
| Predicate | hasLivePerformanceStapleStatus |
P3288
|
FINISHED |
| Object | frequently performed in Green Day concerts |
—
|
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: frequently performed in Green Day concerts | Statement: [Burnout, hasLivePerformanceStapleStatus, frequently performed in Green Day concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePerformanceStapleStatus Context triple: [Burnout, hasLivePerformanceStapleStatus, frequently performed in Green Day concerts]
-
A.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
B.
livePerformanceStapleFor
chosen
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
C.
hasLiveStapleStatusFor
Indicates that an entity currently holds an active or valid staple status for another entity or context.
-
D.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
E.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f9d9848190919aad6cfe14f1cf |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.