Triple
T33466440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot Cove, Maine |
E857057
|
entity |
| Predicate | inspiredTourismIn |
P33524
|
FINISHED |
| Object | Mendocino, California |
—
|
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: Mendocino, California | Statement: [Cabot Cove, Maine, inspiredTourismIn, Mendocino, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredTourismIn Context triple: [Cabot Cove, Maine, inspiredTourismIn, Mendocino, California]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismDraw
chosen
Indicates that one entity attracts tourists or visitor interest to another entity or location.
-
C.
tourismMotivation
Indicates the reasons or driving factors that motivate an entity (typically a person) to engage in tourism or travel activities.
-
D.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
E.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:37 a.m.