Triple
T27444570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bainsford Bridge |
E692234
|
entity |
| Predicate | isOnRouteType |
P13326
|
FINISHED |
| Object | local road |
—
|
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: local road | Statement: [Bainsford Bridge, isOnRouteType, local road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRouteType Context triple: [Bainsford Bridge, isOnRouteType, local road]
-
A.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
B.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
C.
hasRouteType
chosen
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
-
D.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
E.
isOnCircularRoute
Indicates that an entity follows or belongs to a route that forms a closed loop, starting and ending at the same point.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62d90df98819084ea88ad56d524af |
completed | May 2, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:46 p.m.