Triple
T14042851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Found You |
E337887
|
entity |
| Predicate | hasVocalCollaborations |
P54926
|
FINISHED |
| Object | high-profile vocal collaborations |
—
|
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: high-profile vocal collaborations | Statement: [I Found You, hasVocalCollaborations, high-profile vocal collaborations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalCollaborations Context triple: [I Found You, hasVocalCollaborations, high-profile vocal collaborations]
-
A.
featuresVocalCollaborations
chosen
Indicates that the work includes vocal performances by multiple distinct artists collaborating together.
-
B.
hasVocalDuet
Indicates that two entities perform or participate together in a vocal duet.
-
C.
musicalCollaborator
Indicates a relationship where two or more entities work together in creating, performing, or producing music.
-
D.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312b94308190bd0961f5bc719c7b |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.