Triple
T28645699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbe River at Magdeburg |
E725048
|
entity |
| Predicate | intersectedBy |
P416
|
FINISHED |
| Object | Mittelland Canal |
—
|
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: Mittelland Canal | Statement: [Elbe River at Magdeburg, intersectedBy, Mittelland Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intersectedBy Context triple: [Elbe River at Magdeburg, intersectedBy, Mittelland Canal]
-
A.
fieldIntersection
Indicates that two or more fields or domains share a common overlapping area or set of elements.
-
B.
interceptedBy
Indicates that an action, communication, or movement is stopped, captured, or diverted by another agent before reaching its intended target or destination.
-
C.
crossedBy
chosen
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
D.
intersectionRole
Indicates a role or function that an entity specifically holds at the point where two or more entities, paths, or sets intersect.
-
E.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 4:47 a.m.