Triple
T23877103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H 111 |
E592897
|
entity |
| Predicate | associatedLiterarySource |
P10578
|
FINISHED |
| Object | Faust |
—
|
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: Faust | Statement: [H 111, associatedLiterarySource, Faust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLiterarySource Context triple: [H 111, associatedLiterarySource, Faust]
-
A.
literarySource
chosen
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
B.
hasLiteraryConnection
Indicates a relationship in which one entity is connected to another through a literary link, such as authorship, reference, influence, adaptation, or shared appearance in written works.
-
C.
hasLiterarySourceMedium
Indicates that something derives from, is based on, or is expressed through a particular literary medium (such as a book, poem, or script).
-
D.
associatedWithAuthorOfSourceNovel
Indicates a relationship where one entity is connected or linked in some way to the author of the original source novel.
-
E.
literarySourcePublicationYear
Indicates the year in which the literary source associated with an entity was originally published.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc02277c8190b0c15d6525f3b38d |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:15 p.m.