Triple
T22091608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J’avais rêvé d’une autre vie |
E545926
|
entity |
| Predicate | sungByVocalType |
P135747
|
FINISHED |
| Object | mezzo-soprano |
—
|
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: mezzo-soprano | Statement: [J’avais rêvé d’une autre vie, sungByVocalType, mezzo-soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sungByVocalType Context triple: [J’avais rêvé d’une autre vie, sungByVocalType, mezzo-soprano]
-
A.
hasMusicalVocalType
chosen
Indicates that an entity is associated with a specific type or classification of singing voice.
-
B.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
C.
vocalTypeOfSharpless
Indicates that one entity is the vocal type or vocal classification associated with the entity Sharpless.
-
D.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
-
E.
isSungBy
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e5edf08190a6743955bc872417 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.