Triple
T23785750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From the House of the Dead |
E587945
|
entity |
| Predicate | isLastOperaBy |
P103983
|
FINISHED |
| Object | Leoš Janáček |
E418558
|
NE 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: Leoš Janáček | Statement: [From the House of the Dead, isLastOperaBy, Leoš Janáček]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLastOperaBy Context triple: [From the House of the Dead, isLastOperaBy, Leoš Janáček]
-
A.
isLastOrchestralWorkOf
Indicates that the work is the final orchestral composition created by the specified composer or creator.
-
B.
finalOperaOf
chosen
Indicates that one entity is the last opera composed by another entity.
-
C.
isOnlyOperaBy
Indicates that a given opera is the sole opera composed by a particular creator.
-
D.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
E.
appearsInOperaBy
Indicates that one entity (typically a character, role, or element) is featured or takes part in an opera created or composed by another entity.
- F. None of above.
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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c630f81c81909413ba06ae27ebfc |
completed | April 29, 2026, 8:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0f760a06f88190a59004a142cd954b |
completed | May 21, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:17 p.m.