Triple
T25055402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Bizan |
E627502
|
entity |
| Predicate | hasRopewayTerminal |
P160092
|
FINISHED |
| Object | Awa Odori Kaikan side |
—
|
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: Awa Odori Kaikan side | Statement: [Mount Bizan, hasRopewayTerminal, Awa Odori Kaikan side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRopewayTerminal Context triple: [Mount Bizan, hasRopewayTerminal, Awa Odori Kaikan side]
-
A.
hasCableCar
Indicates that one entity possesses, operates, or is served by a cable car system connecting it to other locations or points.
-
B.
hasFunicular
Indicates that one place or facility is equipped with or served by a funicular railway connection to another location.
-
C.
hasMountainRailwayConnectionTo
Indicates that there is a railway line specifically adapted for mountainous terrain that connects one location to another.
-
D.
hasRideSystem
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
E.
hasSkiLiftConnectionTo
Indicates a relationship where one location is directly connected to another by a ski lift, allowing travel between them via that lift.
- F. None of above. chosen
Provenance (4 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 6:09 a.m.