Triple
T25542544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Better Off |
E640209
|
entity |
| Predicate | isLivePerformanceSong |
P130151
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Better Off, isLivePerformanceSong, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLivePerformanceSong Context triple: [Better Off, isLivePerformanceSong, yes]
-
A.
hasLivePerformanceStyle
Indicates that an entity is associated with a particular style or manner of live performance.
-
B.
isSongIn
Indicates that a particular song is contained within or belongs to a specified collection, such as an album, playlist, or soundtrack.
-
C.
hasLivePerformanceStatus
chosen
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
D.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
E.
isForSong
Indicates that something is intended to be used with, associated with, or applicable to a particular song.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f895278881909c376fc06b290c56 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:26 p.m.