Triple
T35032865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derwent River estuary |
E1010824
|
entity |
| Predicate | isLowerReachOf |
P182026
|
FINISHED |
| Object | Derwent River |
—
|
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: Derwent River | Statement: [Derwent River estuary, isLowerReachOf, Derwent River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLowerReachOf Context triple: [Derwent River estuary, isLowerReachOf, Derwent River]
-
A.
isUpperReachOf
Indicates that one segment or portion of a river or watercourse is located upstream from and directly connected to another segment, representing its upper reach.
-
B.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
C.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
D.
existsBelow
Indicates that at least one instance of an entity is located or occurs at a lower level or position relative to another entity.
-
E.
tieneAlcance
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865578d48190bf90e470634fd97d |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.