Triple
T29800147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenswood family |
E756668
|
entity |
| Predicate | operaCharacterBasedOn |
P199265
|
FINISHED |
| Object | Edgardo (Edgar) Ravenswood in Lucia di Lammermoor |
—
|
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: Edgardo (Edgar) Ravenswood in Lucia di Lammermoor | Statement: [Ravenswood family, operaCharacterBasedOn, Edgardo (Edgar) Ravenswood in Lucia di Lammermoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaCharacterBasedOn Context triple: [Ravenswood family, operaCharacterBasedOn, Edgardo (Edgar) Ravenswood in Lucia di Lammermoor]
-
A.
operaCharacterName
Indicates that the subject is the name (or names) of a character appearing in an opera.
-
B.
operaTitleCharacter
Indicates that a character is the title (namesake) character of a given opera.
-
C.
operaActRole
Indicates the role or character that a performer portrays in a specific act of an opera.
-
D.
operaOrOratorioCharacterType
Indicates that the subject is a character type or role as it appears specifically within an opera or an oratorio.
-
E.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: April 29, 2026, 5:17 p.m.