Triple
T37922568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fidelio universe |
E946003
|
entity |
| Predicate | centralCouple |
P4751
|
FINISHED |
| Object | Leonore and Florestan |
—
|
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: Leonore and Florestan | Statement: [Fidelio universe, centralCouple, Leonore and Florestan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCouple Context triple: [Fidelio universe, centralCouple, Leonore and Florestan]
-
A.
centralBinaryComponent
Indicates that an entity functions as one of the primary stellar components in a central binary system.
-
B.
centralSet
Indicates that the referenced set occupies a central or core position within a larger structure, system, or collection, often serving as a primary or focal subset.
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
centralIn
chosen
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
E.
centralConjecture
Indicates that the subject proposition is the main or most important conjecture around which related arguments, results, or discussions are organized.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:20 p.m.