Triple
T9410806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharpness Lock |
E226699
|
entity |
| Predicate | isExitFor |
P79211
|
FINISHED |
| Object | vessels leaving Gloucester and Sharpness Canal to Severn Estuary |
—
|
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: vessels leaving Gloucester and Sharpness Canal to Severn Estuary | Statement: [Sharpness Lock, isExitFor, vessels leaving Gloucester and Sharpness Canal to Severn Estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExitFor Context triple: [Sharpness Lock, isExitFor, vessels leaving Gloucester and Sharpness Canal to Severn Estuary]
-
A.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
B.
isMajorExitOf
chosen
Indicates that one location serves as a primary or significant exit point from another location or route.
-
C.
hasExits
Indicates that an entity provides one or more ways out or routes leading from it to other locations or states.
-
D.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
E.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5255e4fc81908bf2f69c9a12ef83 |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.