Triple
T7598466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigan flight of locks |
E179918
|
entity |
| Predicate | hasLockNumberRange |
P73976
|
FINISHED |
| Object | locks 65 to 85 on Leeds and Liverpool Canal |
—
|
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: locks 65 to 85 on Leeds and Liverpool Canal | Statement: [Wigan flight of locks, hasLockNumberRange, locks 65 to 85 on Leeds and Liverpool Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockNumberRange Context triple: [Wigan flight of locks, hasLockNumberRange, locks 65 to 85 on Leeds and Liverpool Canal]
-
A.
hasNumberOfLocks
Indicates the quantity of locks that an entity possesses or is equipped with.
-
B.
hasLockNumber
chosen
Indicates that an entity is associated with a specific lock identified by a number.
-
C.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
D.
hasLockType
Indicates that an entity is associated with or uses a specific type or category of lock.
-
E.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d67cf88190a3202c07f7cea7df |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.