Triple
T33462150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erik (the Phantom of the Opera) |
E856946
|
entity |
| Predicate | communicatesAs |
P77900
|
FINISHED |
| Object | disembodied voice to Christine Daaé |
—
|
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: disembodied voice to Christine Daaé | Statement: [Erik (the Phantom of the Opera), communicatesAs, disembodied voice to Christine Daaé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicatesAs Context triple: [Erik (the Phantom of the Opera), communicatesAs, disembodied voice to Christine Daaé]
-
A.
communicatedAs
chosen
Indicates that one entity is expressed, conveyed, or presented in the form, manner, or role of another.
-
B.
communicatesFrom
Indicates that information, messages, or signals are sent or expressed from one entity to another.
-
C.
speaksWith
Indicates that one entity engages in spoken communication or conversation with another entity.
-
D.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
E.
communicationTrait
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:37 a.m.