Triple
T16650984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Recordings 2004 |
E404600
|
entity |
| Predicate | featuresLivePerformancesOf |
P48738
|
FINISHED |
| Object | songs by Keane |
—
|
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: songs by Keane | Statement: [Live Recordings 2004, featuresLivePerformancesOf, songs by Keane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLivePerformancesOf Context triple: [Live Recordings 2004, featuresLivePerformancesOf, songs by Keane]
-
A.
livePerformanceFeature
chosen
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
B.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
C.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
D.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
E.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf6cfc481909b183348c407e046 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.