Triple
T33293217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livin' Inside Your Love |
E852369
|
entity |
| Predicate | featuresVocalPerformances |
P140122
|
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: [Livin' Inside Your Love, featuresVocalPerformances, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVocalPerformances Context triple: [Livin' Inside Your Love, featuresVocalPerformances, true]
-
A.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
B.
featuresVocalist
Indicates that one entity (such as a song, track, or performance) includes another entity serving as a vocalist or featured singer.
-
C.
providedVocalPerformanceFor
Indicates that one entity delivered or contributed a vocal performance in support of, or as part of, another entity’s work, event, or production.
-
D.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
E.
featuresVocal
chosen
Indicates that one entity includes or presents the vocal performance or voice of another entity.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a019037edbc8190bdaec436ac2fcec6 |
completed | May 11, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_6a018fe05a34819080068f588b5ff80c |
completed | May 11, 2026, 8:14 a.m. |
Created at: May 1, 2026, 1:33 a.m.