Triple
T28813370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 奥穂高岳 |
E727574
|
entity |
| Predicate | 主なルート |
P127422
|
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.
主な進路
Indicates the primary path, course, or direction typically taken or chosen in a given context.
-
B.
firstMajorRoute
chosen
Indicates that the specified route is the primary or earliest major route associated with an entity (such as a location, project, or network).
-
C.
primaryRouteThrough
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
D.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
E.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.