Triple
T27370873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nara Station |
E690313
|
entity |
| Predicate | isMajorGatewayForTourism |
P33155
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nara Station, isMajorGatewayForTourism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorGatewayForTourism Context triple: [Nara Station, isMajorGatewayForTourism, yes]
-
A.
isMajorTourismRoute
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
B.
isMajorStopForTourists
Indicates that a location is a primary or frequently visited destination for tourists.
-
C.
hasTourismFunction
chosen
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
D.
isMajorInternationalGatewayFor
Indicates that one entity serves as a primary, globally significant access point or hub for another entity’s international connections or flows.
-
E.
hasTourismAuthority
Indicates that an entity holds official responsibility or power to manage, regulate, or oversee tourism-related activities for another entity or area.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 12:18 p.m.