Triple
T15696976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbwe Gate |
E380486
|
entity |
| Predicate | associatedRoutePopularity |
P43486
|
FINISHED |
| Object | low to moderate |
—
|
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: low to moderate | Statement: [Umbwe Gate, associatedRoutePopularity, low to moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRoutePopularity Context triple: [Umbwe Gate, associatedRoutePopularity, low to moderate]
-
A.
popularityRelativeToOtherRoutes
chosen
Indicates how popular a given route is compared to other available routes.
-
B.
isMostPopularRouteOn
Indicates that a particular route is the most frequently chosen or favored option on a given transportation line, network, or service.
-
C.
popularRouteVia
Indicates that a route between two locations commonly or frequently passes through a specified intermediate point or path.
-
D.
popularRouteOn
Indicates that a particular route is frequently used or favored on a given transportation line, service, or network.
-
E.
routeImportance
Indicates the relative significance or priority of a route compared to other possible routes, typically in terms of usefulness, relevance, or preference.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.