Triple
T37756068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurleston Junction |
E941115
|
entity |
| Predicate | numberOfLocksNearby |
—
|
GENERATED |
| Object | 4 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfLocksNearby Context triple: [Hurleston Junction, numberOfLocksNearby, 4]
-
A.
hasNearbyLock
chosen
Indicates that one entity has a lock located in close physical proximity to it.
-
B.
hasNumberOfLocks
Indicates the quantity of locks that an entity possesses or is equipped with.
-
C.
hasLockers
Indicates that one entity provides or contains lockers that are available for use by another entity.
-
D.
hasLockNumber
Indicates that an entity is associated with a specific lock identified by a number.
-
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 (1 batch)
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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.