Triple
T15936834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube River Basin Management Plan |
E386460
|
entity |
| Predicate | coordinatedAtLevel |
P121056
|
FINISHED |
| Object | basin-wide |
—
|
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: basin-wide | Statement: [Danube River Basin Management Plan, coordinatedAtLevel, basin-wide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatedAtLevel Context triple: [Danube River Basin Management Plan, coordinatedAtLevel, basin-wide]
-
A.
coordinatedWith
Indicates that two or more entities have worked together in an organized, cooperative manner toward a shared task, goal, or activity.
-
B.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
C.
coordinatedFrom
Indicates that an action, event, or process is organized, directed, or managed starting from a particular source location or entity.
-
D.
cooperatingLevel
Indicates the degree or intensity to which two or more entities are working together toward a shared goal or activity.
-
E.
ordinationLevel
Indicates the hierarchical rank or degree of authority assigned to an entity within an ordered or structured system.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69e17d48cc9c8190b03fd07ae2e9dfd8 |
completed | April 17, 2026, 12:22 a.m. |
Created at: April 10, 2026, 4:53 a.m.