Triple

T37864726
Position Surface form Disambiguated ID Type / Status
Subject 嵯峨野線 E944438 entity
Predicate 観光地へのアクセス P17187 FINISHED
Object 嵐山エリア 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: 嵐山エリア | Statement: [嵯峨野線, 観光地へのアクセス, 嵐山エリア]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 観光地へのアクセス
Context triple: [嵯峨野線, 観光地へのアクセス, 嵐山エリア]
  • A. touristAccess chosen
    Indicates that a place or resource is available for use or visitation by tourists.
  • B. tourAccess
    Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
  • C. touristGatewayTo
    Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
  • D. hasScenicAccessTo
    Indicates that one place or object provides a visually appealing or notable view of another place or object.
  • 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_69f76eee2f9c8190b1272aa2ee55ebf5 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbae559a8819086ef839973f8d9b2 completed May 6, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69fbb1440fa08190abf25ba684f75b6e completed May 6, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:19 p.m.