Triple
T29396986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aller river basin |
E745525
|
entity |
| Predicate | hasMainRiverMouthLocation |
P17878
|
FINISHED |
| Object | near Verden (Aller) |
—
|
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: near Verden (Aller) | Statement: [Aller river basin, hasMainRiverMouthLocation, near Verden (Aller)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainRiverMouthLocation Context triple: [Aller river basin, hasMainRiverMouthLocation, near Verden (Aller)]
-
A.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
B.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
C.
hasKeyRiverMouth
chosen
Indicates that a geographic entity has a primary river mouth located within or associated with it.
-
D.
hasHumanSettlementAtMouth
Indicates that a human settlement is located at the mouth (outflow point) of a geographic feature such as a river or valley.
-
E.
isMainRhineBranchInNetherlands
Indicates that a river segment is the principal branch of the Rhine within the territory of the Netherlands.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: April 28, 2026, 2:47 p.m.