Triple
T28381530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of Dresden |
E718901
|
entity |
| Predicate | literature |
P27711
|
FINISHED |
| Object | Slaughterhouse-Five |
—
|
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: Slaughterhouse-Five | Statement: [bombing of Dresden, literature, Slaughterhouse-Five]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literature Context triple: [bombing of Dresden, literature, Slaughterhouse-Five]
-
A.
inLiterature
chosen
Indicates that a work, concept, or entity is mentioned, discussed, or represented within a piece of literature.
-
B.
literatureType
Indicates the specific category or genre of literature that characterizes or classifies a given work or text.
-
C.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
-
D.
literaryInterest
Indicates that one entity has an interest in, appreciation of, or engagement with the literary works or writings of another entity.
-
E.
literaryUniverse
Indicates that two or more works of literature exist within the same fictional universe or continuity, sharing settings, characters, or canonical events.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 1:06 a.m.