Triple
T36450505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot Cove |
E897994
|
entity |
| Predicate | fictionalStateRegion |
P114636
|
FINISHED |
| Object | Maine coast |
—
|
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: Maine coast | Statement: [Cabot Cove, fictionalStateRegion, Maine coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalStateRegion Context triple: [Cabot Cove, fictionalStateRegion, Maine coast]
-
A.
fictionalGeographicRegion
Indicates that a geographic region exists only in fiction or imagination rather than in the real world.
-
B.
fictionalJurisdiction
Indicates that one entity has legal authority or governance over another within an invented or imaginary legal system or territory.
-
C.
fictionalSettingRegion
chosen
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
D.
stateOrRegion
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
E.
inUSStateRegion
Indicates that one entity is located within, or belongs to, a specific region of a U.S. state.
- 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_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:10 p.m.