Triple
T28262590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Près des remparts de Séville |
E712619
|
entity |
| Predicate | singerInteractsWithCharacter |
P164219
|
FINISHED |
| Object | Don José |
—
|
NE NERFINISHED |
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: Don José | Statement: [Près des remparts de Séville, singerInteractsWithCharacter, Don José]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singerInteractsWithCharacter Context triple: [Près des remparts de Séville, singerInteractsWithCharacter, Don José]
-
A.
singerForCharacter
Indicates that one entity serves as the singing voice or vocalist for a particular character.
-
B.
sungByCharacter
Indicates that a song or musical piece is performed vocally by a specific character.
-
C.
performerCharacterName
Indicates that a performer is associated with or portrays a specific character name in a performance or work.
-
D.
performedAsSingerIn
Indicates that an entity took part in a performance specifically in the role of a singer within a particular event, production, or context.
-
E.
singerInNarrative
Indicates that one entity serves as the singer or vocal performer within the context or storyline of the other entity (the narrative).
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64419e5f881908d08370af0445383 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 27, 2026, 11:12 p.m.