Triple
T3697961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Local |
E78503
|
entity |
| Predicate | routePattern |
P32810
|
FINISHED |
| Object | city routes |
—
|
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: city routes | Statement: [Metro Local, routePattern, city routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routePattern Context triple: [Metro Local, routePattern, city routes]
-
A.
URLPattern
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
-
B.
routeSegment
Indicates a specific portion of a larger route that directly connects two points or locations within that route.
-
C.
route
Indicates that one entity serves as a path or course used to travel or move between locations associated with another entity.
-
D.
routeStructure
chosen
Indicates the structural or organizational relationship between a route and its constituent segments, paths, or connections.
-
E.
auxiliaryRoutePattern
Indicates that one route serves as an auxiliary or supplemental path that follows or branches from a primary route according to a specific pattern or configuration.
- 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_69adc512ba188190a15bcacafac3f476 |
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.