Triple
T29533254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medway navigation locks |
E749263
|
entity |
| Predicate | upstreamLimit |
P118310
|
FINISHED |
| Object | Tonbridge |
—
|
NE NERFINISHED |
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: Tonbridge | Statement: [Medway navigation locks, upstreamLimit, Tonbridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upstreamLimit Context triple: [Medway navigation locks, upstreamLimit, Tonbridge]
-
A.
upstreamLimitOf
chosen
Indicates that one entity defines or constrains the maximum upstream capacity, flow, or allowable limit for another entity in a system or process.
-
B.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
C.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
D.
innerLimit
Indicates a boundary or maximum value that applies within a specified internal or constrained context of something.
-
E.
definesLimitOf
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cc44fd0819081167945377cf3c4 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:55 p.m.