Triple
T3696474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbwe Route |
E78470
|
entity |
| Predicate | trafficRelativeToOtherRoutes |
P43486
|
FINISHED |
| Object | less-traveled |
—
|
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: less-traveled | Statement: [Umbwe Route, trafficRelativeToOtherRoutes, less-traveled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficRelativeToOtherRoutes Context triple: [Umbwe Route, trafficRelativeToOtherRoutes, less-traveled]
-
A.
popularityRelativeToOtherRoutes
chosen
Indicates how popular a given route is compared to other available routes.
-
B.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
C.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
D.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
E.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc50f9ad88190a926042fa73d65dc |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.