Triple
T35211519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braunston Junction |
E1016691
|
entity |
| Predicate | hasNearbyLockFlight |
P197679
|
FINISHED |
| Object | Braunston Locks |
—
|
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: Braunston Locks | Statement: [Braunston Junction, hasNearbyLockFlight, Braunston Locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyLockFlight Context triple: [Braunston Junction, hasNearbyLockFlight, Braunston Locks]
-
A.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
-
B.
hasNearbyLock
Indicates that one entity has a lock located in close physical proximity to it.
-
C.
nearbyCanalLockFlight
chosen
Indicates that one entity is located close to a sequence of canal locks (a lock flight) associated with a canal.
-
D.
hasScheduledFlights
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
E.
numberOfLocksInMainFlight
Indicates the total count of locks present in the main flight (primary sequence) of a canal or lock system.
- 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_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:02 p.m.