Triple
T4952077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristan und Isolde |
E111190
|
entity |
| Predicate | famousExcerpt |
P52554
|
FINISHED |
| Object | Prelude |
—
|
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: Prelude | Statement: [Tristan und Isolde, famousExcerpt, Prelude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousExcerpt Context triple: [Tristan und Isolde, famousExcerpt, Prelude]
-
A.
famousWriterAssociated
Indicates a relationship where a well-known or renowned writer is connected or linked to a particular entity (such as a work, place, event, or organization).
-
B.
notableQuote
Indicates that one entity is a significant or well-known quotation attributed to, recorded by, or strongly associated with another entity.
-
C.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
D.
fameFor
chosen
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
famousPlay
Indicates that the subject is a well-known or widely recognized theatrical play.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b6a5d481909ad6f5e0b752496c |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.