Triple
T10715854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Turn to You |
E252664
|
entity |
| Predicate | vocalPerformanceReception |
P95611
|
FINISHED |
| Object | praised by critics |
—
|
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: praised by critics | Statement: [I Turn to You, vocalPerformanceReception, praised by critics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPerformanceReception Context triple: [I Turn to You, vocalPerformanceReception, praised by critics]
-
A.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
B.
hasVocalPerformanceBy
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.
vocalForces
Indicates a relationship where one entity uses vocal expression (such as speech, singing, or sound) to exert influence, pressure, or compulsion on another entity.
- F. None of above. chosen
Provenance (4 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6ff3320448190899c56b02a7f5ffa |
completed | April 9, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:13 p.m.