Triple
T6331599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford Canal |
E142392
|
entity |
| Predicate | originalRouteCharacteristic |
P8860
|
FINISHED |
| Object | very winding |
—
|
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: very winding | Statement: [Oxford Canal, originalRouteCharacteristic, very winding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRouteCharacteristic Context triple: [Oxford Canal, originalRouteCharacteristic, very winding]
-
A.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
B.
routeNetworkCharacteristic
chosen
Indicates a relationship where a specific characteristic or property is attributed to a route within a network.
-
C.
formerRouteNumber
Indicates that an entity previously had a specific route number before being renumbered, discontinued, or otherwise changed.
-
D.
transportationCharacteristic
Indicates a specific property, feature, or quality that characterizes a mode, means, or instance of transportation.
-
E.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06514cbe8819096dbeb17ccb3e3d5 |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.