Triple
T1384310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunbury-on-Thames |
E29808
|
entity |
| Predicate | riverReach |
P5565
|
FINISHED |
| Object | non-tidal Thames reach above Teddington Lock |
—
|
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 reach above Teddington Lock | Statement: [Sunbury-on-Thames, riverReach, non-tidal Thames reach above Teddington Lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverReach Context triple: [Sunbury-on-Thames, riverReach, non-tidal Thames reach above Teddington Lock]
-
A.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
B.
riverConfluence
Indicates the location or relationship where two or more rivers or streams join and merge into a single watercourse.
-
C.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
D.
waterwayServed
chosen
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
waterwaySystem
Indicates that one entity is part of, or belongs to, a connected network of waterways associated with another 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33896548190b44f70c9aaaed9b6 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.