Triple
T36417265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Corpse Danced at Midnight |
E897044
|
entity |
| Predicate | hasFictionalAuthorResidence |
P47688
|
FINISHED |
| Object | Cabot Cove, Maine |
—
|
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: Cabot Cove, Maine | Statement: [The Corpse Danced at Midnight, hasFictionalAuthorResidence, Cabot Cove, Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalAuthorResidence Context triple: [The Corpse Danced at Midnight, hasFictionalAuthorResidence, Cabot Cove, Maine]
-
A.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
-
B.
worksAtFictionalPlace
Indicates that an entity is employed at or associated with performing work in a fictional or imaginary location.
-
C.
residesInFictionalLocation
chosen
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
D.
stateOfFictionalResidence
Indicates the state or region in which a fictional character’s residence is located.
-
E.
livesNearFictionalPlace
Indicates that one entity resides in close proximity to a fictional or imaginary location.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 3, 2026, 4:10 p.m.