Triple
T3644593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sound and the Fury (2014 film) |
E77266
|
entity |
| Predicate | literarySourceGenre |
P22130
|
FINISHED |
| Object | modernist novel |
—
|
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: modernist novel | Statement: [The Sound and the Fury (2014 film), literarySourceGenre, modernist novel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySourceGenre Context triple: [The Sound and the Fury (2014 film), literarySourceGenre, modernist novel]
-
A.
literaryGenreOfWork
chosen
Indicates that a work belongs to or is classified under a particular literary genre.
-
B.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
C.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
D.
inLiterature
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
E.
literaryFeature
Indicates a relationship where something possesses or exhibits a characteristic, device, or stylistic element used in literature.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35c28908190b253f4835918a2b4 |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.