Triple
T37757364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usui Pass |
E941152
|
entity |
| Predicate | transportRouteType |
P11026
|
FINISHED |
| Object | road route |
—
|
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: road route | Statement: [Usui Pass, transportRouteType, road route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportRouteType Context triple: [Usui Pass, transportRouteType, road route]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
C.
hasTransportRoute
chosen
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
E.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: May 3, 2026, 4:19 p.m.