Triple
T6940031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunbury Lock |
E160648
|
entity |
| Predicate | waterwaySection |
P49101
|
FINISHED |
| Object | non-tidal Thames |
—
|
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: non-tidal Thames | Statement: [Sunbury Lock, waterwaySection, non-tidal Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwaySection Context triple: [Sunbury Lock, waterwaySection, non-tidal Thames]
-
A.
waterwayJunction
Indicates a point where two or more waterways meet, intersect, or branch from one another.
-
B.
stateWaterway
Indicates that a waterway is located within, passes through, or is otherwise geographically associated with a particular state.
-
C.
partOfWaterway
chosen
Indicates that one water-related feature is a constituent or segment of a larger waterway system.
-
D.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
E.
waterwayLinkBetween
Indicates a connection or linkage between two waterways, such as rivers, canals, or channels, through which water can flow or navigation can occur.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.