Triple
T27574689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuckin' in the Bushes |
E699426
|
entity |
| Predicate | isLiveShowOpenerFor |
P104295
|
FINISHED |
| Object | Oasis |
—
|
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: Oasis | Statement: [Fuckin' in the Bushes, isLiveShowOpenerFor, Oasis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLiveShowOpenerFor Context triple: [Fuckin' in the Bushes, isLiveShowOpenerFor, Oasis]
-
A.
isConcertOpener
chosen
Indicates that one performer, act, or event serves as the opening performance for another concert or main act.
-
B.
isPerformedLiveBy
Indicates that an action, event, or performance occurs in real time in front of an audience and is carried out by the specified entity.
-
C.
isLive
Indicates that an entity is currently broadcasting or occurring in real time, as opposed to being pre-recorded or inactive.
-
D.
hasLivePerformanceOrigin
Indicates that something originates from, or is derived from, a live performance event.
-
E.
isPostShowFor
Indicates that one event, program, or segment occurs immediately after and is associated with a particular show (i.e., it is the follow-up or after-show for that show).
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f62fef2d9c8190b1b3c1e8c2afe16f |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:01 p.m.