Triple
T29808292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plug In Baby |
E756892
|
entity |
| Predicate | hasLiveRelease |
P22087
|
FINISHED |
| Object | Hullabaloo: Live at Le Zenith, Paris |
—
|
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: Hullabaloo: Live at Le Zenith, Paris | Statement: [Plug In Baby, hasLiveRelease, Hullabaloo: Live at Le Zenith, Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveRelease Context triple: [Plug In Baby, hasLiveRelease, Hullabaloo: Live at Le Zenith, Paris]
-
A.
hasLiveSingleRelease
Indicates that an entity has released a live recording of a single as an official release.
-
B.
hasLiveVideoRelease
Indicates that an entity has an associated release of a live video recording.
-
C.
hasLiveAlbumReleaseType
Indicates that a musical work or recording has a release type specifically classified as a live album.
-
D.
hasRelease
chosen
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
E.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 29, 2026, 5:22 p.m.