Triple
T1489470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aller |
E29543
|
entity |
| Predicate | tributaryDirection |
P415
|
FINISHED |
| Object | right tributary of the Weser |
—
|
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: right tributary of the Weser | Statement: [Aller, tributaryDirection, right tributary of the Weser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tributaryDirection Context triple: [Aller, tributaryDirection, right tributary of the Weser]
-
A.
drainageDirection
Indicates the direction in which water or other fluids flow or are drained away from a given point or area.
-
B.
tributary
chosen
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
-
C.
distributaryOf
Indicates that one watercourse branches off from a main river or stream and carries its water away, rather than feeding into it.
-
D.
drainageDivideOf
Indicates that one geographic feature functions as the drainage divide (separating water flow into different basins) for another feature or area.
-
E.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a6095481909e9d406ac9a41828 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.