Triple
T35211530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norton Junction |
E1016692
|
entity |
| Predicate | hasRouteDiverging |
P124470
|
FINISHED |
| Object | Grand Union Canal main line |
—
|
NE NERFINISHED |
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: Grand Union Canal main line | Statement: [Norton Junction, hasRouteDiverging, Grand Union Canal main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteDiverging Context triple: [Norton Junction, hasRouteDiverging, Grand Union Canal main line]
-
A.
hasDivergence
Indicates that there is a difference, deviation, or separation between two otherwise related entities, states, or paths.
-
B.
hasMultipleRoutes
chosen
Indicates that there is more than one distinct route or path available between the related entities.
-
C.
hasFlankingRoute
Indicates that one location or position can be reached or bypassed via an alternative side or rear route that avoids direct approach.
-
D.
hadRoute
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
E.
hasSeparateDescentRoute
Indicates that an entity follows a different or distinct path or route for descent compared to another entity or route.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:02 p.m.