Triple
T33068556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inglesham Lock |
E846168
|
entity |
| Predicate | positionOnCanal |
P34002
|
FINISHED |
| Object | western end |
—
|
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: western end | Statement: [Inglesham Lock, positionOnCanal, western end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCanal Context triple: [Inglesham Lock, positionOnCanal, western end]
-
A.
positionInCanal
chosen
Indicates that an entity occupies a specific location within a canal.
-
B.
nearbyCanal
Indicates that one entity is located close to or in the immediate vicinity of a canal.
-
C.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
D.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
E.
notableCanal
Indicates that there exists a canal that is especially significant, famous, or otherwise notable in relation to the subject.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 1:25 a.m.