Triple
T3517758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biltmore Winery |
E74347
|
entity |
| Predicate | partOfTourism |
P32586
|
FINISHED |
| Object | Biltmore Estate visitor experience |
—
|
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: Biltmore Estate visitor experience | Statement: [Biltmore Winery, partOfTourism, Biltmore Estate visitor experience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfTourism Context triple: [Biltmore Winery, partOfTourism, Biltmore Estate visitor experience]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
C.
isPartOfTouristArea
chosen
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
D.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
E.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc32f90081908960acb3e94402be |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.