Triple
T29433305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ingrebourne |
E746496
|
entity |
| Predicate | isTributaryDirection |
P114978
|
FINISHED |
| Object | left-bank tributary 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: left-bank tributary of the River Thames | Statement: [River Ingrebourne, isTributaryDirection, left-bank tributary of the River Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTributaryDirection Context triple: [River Ingrebourne, isTributaryDirection, left-bank tributary of the River Thames]
-
A.
isNaturalTributaryOf
Indicates that one watercourse flows naturally into another, contributing its water as a tributary without artificial diversion.
-
B.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
C.
hasTributaryRelation
Indicates a relationship where one entity serves as a tributary, paying regular tribute or acknowledging subordination to another entity.
-
D.
hasTributaryType
Indicates that one watercourse is classified as a specific type of tributary in relation to another water body.
-
E.
tributarySide
chosen
Indicates the side (e.g., left or right bank) of a main watercourse on which a tributary joins it.
- 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66acb070c8190a3f751d34e7dcf99 |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:14 p.m.