Triple
T13413524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kettwiger See |
E320149
|
entity |
| Predicate | managesFunction |
P109812
|
FINISHED |
| Object | flow regulation of Ruhr |
—
|
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: flow regulation of Ruhr | Statement: [Kettwiger See, managesFunction, flow regulation of Ruhr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesFunction Context triple: [Kettwiger See, managesFunction, flow regulation of Ruhr]
-
A.
maneFunction
Indicates that an entity’s primary or central function, role, or purpose is being specified or described.
-
B.
managementIs
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
C.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
D.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
E.
organizationalFunction
Indicates the role, purpose, or primary activity that an organization performs within a broader system or context.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb556948190af008c88e5bbf051 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:35 p.m.