Triple
T29180841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faust Symphony |
E739739
|
entity |
| Predicate | literaryBasis |
P10578
|
FINISHED |
| Object | Goethe’s Faust Part I |
—
|
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: Goethe’s Faust Part I | Statement: [Faust Symphony, literaryBasis, Goethe’s Faust Part I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryBasis Context triple: [Faust Symphony, literaryBasis, Goethe’s Faust Part I]
-
A.
literarySource
chosen
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
B.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
C.
literaryCenter
Indicates that a location functions as a primary hub or focal point for literary activity, such as writing, publishing, or literary culture.
-
D.
inLiterature
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
E.
literaryInterest
Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings of another entity.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 11:57 a.m.