Triple
T28607840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube River at Ulm |
E724100
|
entity |
| Predicate | hasSourceUpstreamIn |
P86522
|
FINISHED |
| Object | Black Forest |
—
|
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: Black Forest | Statement: [Danube River at Ulm, hasSourceUpstreamIn, Black Forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSourceUpstreamIn Context triple: [Danube River at Ulm, hasSourceUpstreamIn, Black Forest]
-
A.
hasUpstreamArea
Indicates that one geographic or hydrologic area lies upstream of and contributes flow or influence to another area.
-
B.
hasParentAccordingToSource
Indicates that an entity is recorded as the parent of another entity according to a specified source or authority.
-
C.
containsSourceOf
chosen
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
D.
hasUpstreamImpactOn
Indicates that one entity’s actions, changes, or outputs affect another entity that is positioned earlier in a process, flow, or dependency chain.
-
E.
basedOnSourcesUpTo
Indicates that something is derived, justified, or determined using information available only up to a specified point in time.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 4:28 a.m.