Triple
T32658855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovebug |
E834936
|
entity |
| Predicate | hasLiveAcousticVersions |
P147087
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lovebug, hasLiveAcousticVersions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveAcousticVersions Context triple: [Lovebug, hasLiveAcousticVersions, true]
-
A.
hasLiveAcousticVersion
chosen
Indicates that an entity has a corresponding version that is performed live using acoustic instrumentation.
-
B.
hasAcousticVersionBy
Indicates that one entity is an acoustic version of another, created or performed by a specified agent.
-
C.
hasNotableLiveAcousticPerformances
Indicates that the subject has given live performances of acoustic versions of their work that are considered notable or significant.
-
D.
hasAudioReleases
Indicates that an entity has associated audio-format releases (such as recordings, tracks, or audio editions) that have been published or made available.
-
E.
hasLiveRecordingOfAlbum
Indicates that a live recording exists that captures performances of the tracks from a specific studio album.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 1:08 a.m.