Triple
T29721976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire (L’enfant et les sortilèges) |
E752077
|
entity |
| Predicate | oftenSungBy |
P32287
|
FINISHED |
| Object | coloratura 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: coloratura soprano | Statement: [Fire (L’enfant et les sortilèges), oftenSungBy, coloratura soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenSungBy Context triple: [Fire (L’enfant et les sortilèges), oftenSungBy, coloratura soprano]
-
A.
singsWith
Indicates that two or more entities perform singing together, jointly participating in a vocal musical activity.
-
B.
isSungBy
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
-
C.
alsoSungTo
Indicates that a song or musical piece is additionally performed or directed toward another recipient or audience beyond the primary one.
-
D.
isTraditionallySungBy
chosen
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
E.
singsSongsPerformedBy
Indicates that one entity sings songs that are performed by 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 7:37 p.m.