Triple
T464978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Glyme |
E8424
|
entity |
| Predicate | isInDrainageBasin |
P1559
|
FINISHED |
| Object | River Thames basin |
—
|
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: River Thames basin | Statement: [River Glyme, isInDrainageBasin, River Thames basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInDrainageBasin Context triple: [River Glyme, isInDrainageBasin, River Thames basin]
-
A.
drainageBasin
chosen
Indicates the area of land where all precipitation and surface water flow are collected and drained toward a particular river, lake, or other water body.
-
B.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
C.
basinType
Indicates the specific kind or classification of a basin associated with an entity (e.g., by form, function, or hydrological role).
-
D.
drainageBasinArea
Indicates the total surface area of land from which precipitation and runoff drain into a particular water body or watershed.
-
E.
basin
Indicates a geographic area where surface water drains into a common outlet, such as a river, lake, or ocean.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd5b6b48190ae23968135cf6417 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.