Triple
T11040935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yōkaichi Interchange |
E261011
|
entity |
| Predicate | hasAccessDirection |
P42312
|
FINISHED |
| Object | to Meishin Expressway |
—
|
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: to Meishin Expressway | Statement: [Yōkaichi Interchange, hasAccessDirection, to Meishin Expressway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessDirection Context triple: [Yōkaichi Interchange, hasAccessDirection, to Meishin Expressway]
-
A.
accessDirection
chosen
Indicates the direction or orientation from which access to something is obtained or permitted.
-
B.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
C.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
D.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
E.
hasAccessRouteTo
Indicates that one entity possesses a path, connection, or means of reaching or interacting with another entity.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7980050948190ae7b187da5b776ca |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.