Triple
T7683883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift Rapids Lock |
E174063
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object |
Lock 43
Lock 43, also known as Swift Rapids Lock, is a large lock on Ontario’s Trent–Severn Waterway notable for its significant lift and remote, scenic location.
|
E682062
|
NE FINISHED |
How this triple was built (4 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: Lock 43 | Statement: [Swift Rapids Lock, hasAlternativeName, Lock 43]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lock 43 Context triple: [Swift Rapids Lock, hasAlternativeName, Lock 43]
-
A.
Lock 45
Lock 45 is the final lock on Ontario’s Trent–Severn Waterway, located at Port Severn where the canal meets Georgian Bay.
-
B.
Lock 21
Lock 21 is one of the numbered canal locks at Merrickville on Canada’s historic Rideau Canal system.
-
C.
Lock 22
Lock 22 is one of the numbered canal locks at Merrickville on Canada’s historic Rideau Canal waterway.
-
D.
Teston Lock
Teston Lock is a navigation lock on the River Medway in Kent, England, used to manage river levels and enable boat passage.
-
E.
Lock 11 and Weir
Lock 11 and Weir is a historic river navigation structure on the Murray River at Mildura, Australia, known for regulating water levels and enabling boat passage while serving as a popular local tourist attraction.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Lock 43 Triple: [Swift Rapids Lock, hasAlternativeName, Lock 43]
Generated description
Lock 43, also known as Swift Rapids Lock, is a large lock on Ontario’s Trent–Severn Waterway notable for its significant lift and remote, scenic location.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lock 43 Target entity description: Lock 43, also known as Swift Rapids Lock, is a large lock on Ontario’s Trent–Severn Waterway notable for its significant lift and remote, scenic location.
-
A.
Lock 45
Lock 45 is the final lock on Ontario’s Trent–Severn Waterway, located at Port Severn where the canal meets Georgian Bay.
-
B.
Lock 21
Lock 21 is one of the numbered canal locks at Merrickville on Canada’s historic Rideau Canal system.
-
C.
Lock 22
Lock 22 is one of the numbered canal locks at Merrickville on Canada’s historic Rideau Canal waterway.
-
D.
Teston Lock
Teston Lock is a navigation lock on the River Medway in Kent, England, used to manage river levels and enable boat passage.
-
E.
Lock 11 and Weir
Lock 11 and Weir is a historic river navigation structure on the Murray River at Mildura, Australia, known for regulating water levels and enabling boat passage while serving as a popular local tourist attraction.
- F. None of above. chosen
Provenance (5 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7021ed6008190a1522b46110e677e |
completed | March 27, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8a257af0c8190ba1a2693a42b9ebe |
completed | March 29, 2026, 3:53 a.m. |
| NEDg | Description generation | batch_69c8a7d596b081909f79b2a741b10a8f |
completed | March 29, 2026, 4:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c8a82f67308190be0636dd783f30f5 |
completed | March 29, 2026, 4:18 a.m. |
Created at: March 27, 2026, 4:01 p.m.