Triple
T26108963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovin’ You for Life |
E658627
|
entity |
| Predicate | basedOnVocalsBy |
P44280
|
FINISHED |
| Object | The Notorious B.I.G. |
—
|
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: The Notorious B.I.G. | Statement: [Lovin’ You for Life, basedOnVocalsBy, The Notorious B.I.G.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnVocalsBy Context triple: [Lovin’ You for Life, basedOnVocalsBy, The Notorious B.I.G.]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
C.
vocal
Indicates that an entity produces or is characterized by audible sounds, speech, or vocalizations.
-
D.
vocalInfluence
Indicates that one entity affects, shapes, or modifies another entity through vocal expression, such as speech, tone, or sound.
-
E.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 26, 2026, 8 p.m.