Triple
T15459685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Lock and Weir |
E371863
|
entity |
| Predicate | upstreamLimitOf |
P118310
|
FINISHED |
| Object | tideway of the River 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: tideway of the River Thames | Statement: [Richmond Lock and Weir, upstreamLimitOf, tideway of the River Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upstreamLimitOf Context triple: [Richmond Lock and Weir, upstreamLimitOf, tideway of the River Thames]
-
A.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
B.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
C.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
-
D.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
E.
outerLimitDefinedFrom
Indicates that the outer boundary or maximum extent of one entity is determined or specified based on another entity.
- F. None of above. chosen
Provenance (4 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:32 a.m.