Triple
T36450496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot Cove |
E897994
|
entity |
| Predicate | narrativeReputation |
P181999
|
FINISHED |
| Object | high murder rate |
—
|
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: high murder rate | Statement: [Cabot Cove, narrativeReputation, high murder rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeReputation Context triple: [Cabot Cove, narrativeReputation, high murder rate]
-
A.
reputationInLore
chosen
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
-
B.
refersToPersonReputation
Indicates that something is about, concerns, or makes reference to a particular person's reputation.
-
C.
scopeOfReputation
Indicates the range or extent within which an entity’s reputation is recognized, relevant, or has effect.
-
D.
placeInReputation
Indicates that an entity holds a particular standing, status, or level within a reputation or ranking system.
-
E.
reputationContent
Indicates that some content pertains to, affects, or reflects the reputation of an entity.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:10 p.m.