Triple
T22029953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banquo’s ghost banquet scene |
E544057
|
entity |
| Predicate | BanquoGhostFunction |
P146340
|
FINISHED |
| Object | silent accusation of Macbeth |
—
|
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: silent accusation of Macbeth | Statement: [Banquo’s ghost banquet scene, BanquoGhostFunction, silent accusation of Macbeth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BanquoGhostFunction Context triple: [Banquo’s ghost banquet scene, BanquoGhostFunction, silent accusation of Macbeth]
-
A.
isHauntedLocation
Indicates that a location is supernaturally affected or inhabited by ghosts, spirits, or other paranormal entities.
-
B.
burialPlotGuardedBy
Indicates that a burial plot is protected or watched over by a specified guardian or guarding entity.
-
C.
The Grave_theme
Indicates a relationship where an entity serves as the thematic or symbolic focus associated with a grave or burial context.
-
D.
hasGraveOccupant
Indicates that a grave is occupied by a specific person or entity.
-
E.
The Grave_is
Indicates that something is identified as, located at, or characterized by the grave.
- F. None of above. chosen
Provenance (4 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ed0cb08190aead0838cc62934c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:24 p.m.