Triple
T36395685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tōkai-Hokuriku Expressway |
E896470
|
entity |
| Predicate | connectsTouristArea |
P71264
|
FINISHED |
| Object | Hida region |
—
|
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: Hida region | Statement: [Tōkai-Hokuriku Expressway, connectsTouristArea, Hida region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTouristArea Context triple: [Tōkai-Hokuriku Expressway, connectsTouristArea, Hida region]
-
A.
connectsTouristDestinations
Indicates a relationship where something links or provides a route between multiple tourist destinations.
-
B.
connectsToTouristRegion
chosen
Indicates that one entity has a direct linkage or association to a tourist region, such as through location, access, or service provision.
-
C.
tourArea
Indicates that an entity conducts, offers, or is associated with tours within a specified geographic area or region.
-
D.
containsTouristArea
Indicates that a place or region includes within its boundaries an area primarily designated or recognized for tourism activities.
-
E.
touristGatewayTo
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.