Triple
T35204467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford, Northamptonshire |
E1016495
|
entity |
| Predicate | nearbyCanalLockFlight |
P197679
|
FINISHED |
| Object | Watford 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: Watford Locks | Statement: [Watford, Northamptonshire, nearbyCanalLockFlight, Watford Locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCanalLockFlight Context triple: [Watford, Northamptonshire, nearbyCanalLockFlight, Watford Locks]
-
A.
nearbyCanal
Indicates that one entity is located close to or in the immediate vicinity of a canal.
-
B.
openAirAttraction
Indicates that an attraction or event takes place outdoors in an open-air setting rather than in an enclosed space.
-
C.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
D.
hasCanalLock
Indicates that one entity (typically a canal or waterway) includes or is equipped with a canal lock used to raise and lower boats between stretches of water at different levels.
-
E.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
- F. None of above. chosen
Provenance (4 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 3, 2026, 4:02 p.m.