Triple
T34209659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montecito Inn |
E877617
|
entity |
| Predicate | isLocatedInTourismRegion |
P32586
|
FINISHED |
| Object | Santa Barbara area |
—
|
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: Santa Barbara area | Statement: [Montecito Inn, isLocatedInTourismRegion, Santa Barbara area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInTourismRegion Context triple: [Montecito Inn, isLocatedInTourismRegion, Santa Barbara area]
-
A.
isPartOfTouristArea
chosen
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
B.
connectsToTouristRegion
Indicates that one entity has a direct linkage or association to a tourist region, such as through location, access, or service provision.
-
C.
locatedInWineTourismCorridor
Indicates that something is situated within a designated wine tourism corridor or route.
-
D.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
E.
isPopularTouristDestinationIn
Indicates that a place is widely visited and favored by tourists within a specified geographic area or region.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:55 a.m.