Triple
T30311240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindorf |
E770927
|
entity |
| Predicate | oftenSungByPerformer |
P81375
|
FINISHED |
| Object | same singer as Coppélius |
—
|
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: same singer as Coppélius | Statement: [Lindorf, oftenSungByPerformer, same singer as Coppélius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenSungByPerformer Context triple: [Lindorf, oftenSungByPerformer, same singer as Coppélius]
-
A.
performedAsSingerIn
Indicates that an entity took part in a performance specifically in the role of a singer within a particular event, production, or context.
-
B.
performedSongsBy
Indicates that one entity has performed songs that were created, owned, or associated with another entity.
-
C.
singsSongsPerformedBy
Indicates that one entity sings songs that are performed by another entity.
-
D.
isSungBy
chosen
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
-
E.
singsWith
Indicates that two or more entities perform singing together, jointly participating in a vocal musical activity.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 7:50 p.m.