Triple
T31440517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrenbury |
E802052
|
entity |
| Predicate | hasLockOnCanal |
P85577
|
FINISHED |
| Object | Wrenbury Heath 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: Wrenbury Heath locks | Statement: [Wrenbury, hasLockOnCanal, Wrenbury Heath locks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockOnCanal Context triple: [Wrenbury, hasLockOnCanal, Wrenbury Heath locks]
-
A.
hasCanalLock
chosen
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.
-
B.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
C.
containsCanal
Indicates that one geographical or spatial entity has a canal located within its boundaries or interior.
-
D.
hasCanalFunction
Indicates that something serves the role or performs the function of a canal, such as conveying or channeling a flow (e.g., water, fluids, or traffic).
-
E.
hasCanalParallel
Indicates that one canal runs parallel to another canal without intersecting it.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 30, 2026, 9:05 p.m.