Triple
T2476424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunspach |
E55098
|
entity |
| Predicate | hasTourismLabel |
P530
|
FINISHED |
| Object | village of character |
—
|
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: village of character | Statement: [Hunspach, hasTourismLabel, village of character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourismLabel Context triple: [Hunspach, hasTourismLabel, village of character]
-
A.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
B.
hasTourismRating
Indicates that an entity has been assigned a specific tourism-related quality or rating, reflecting its appeal or suitability for tourists.
-
C.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
D.
hasTourismHub
Indicates that a place functions as a central location or focal point for tourism-related activities, services, or attractions for another place or region.
-
E.
isTouristDestination
chosen
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.