Triple
T28989636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medway catchment |
E734786
|
entity |
| Predicate | partOfRiverBasinDistrict |
P36894
|
FINISHED |
| Object | Thames River Basin District |
—
|
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: Thames River Basin District | Statement: [Medway catchment, partOfRiverBasinDistrict, Thames River Basin District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRiverBasinDistrict Context triple: [Medway catchment, partOfRiverBasinDistrict, Thames River Basin District]
-
A.
basinDistrict
Indicates a relationship where an administrative or geographic district is associated with, or falls within, a particular drainage or river basin.
-
B.
basinPartOf
chosen
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
C.
basinProvince
Indicates a relationship where a geological basin is located within, associated with, or governed by a particular province or administrative region.
-
D.
resourceBasin
Indicates a relationship where a basin serves as a source or reservoir of resources for another entity or area.
-
E.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 28, 2026, 9:16 a.m.