Triple
T34573896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakone Checkpoint |
E887697
|
entity |
| Predicate | onMajorRouteBetween |
P179331
|
FINISHED |
| Object | Kyoto |
—
|
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: Kyoto | Statement: [Hakone Checkpoint, onMajorRouteBetween, Kyoto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onMajorRouteBetween Context triple: [Hakone Checkpoint, onMajorRouteBetween, Kyoto]
-
A.
isMajorRouteThrough
Indicates that a route serves as a primary or significant pathway passing through a specified area or location.
-
B.
hasMajorRouteType
Indicates that an entity is associated with a primary classification of transportation route (such as highway, rail line, or other major route type).
-
C.
hasMajorStructureOnRoute
Indicates that a significant physical structure is located along or directly associated with a particular route.
-
D.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
E.
isMajorTrafficRoute
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72097243c8190a2ee6b2f1bc22585 |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:03 a.m.