Triple
T32107773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raddusch |
E820030
|
entity |
| Predicate | hasNearbyCanalSystem |
P151163
|
FINISHED |
| Object | Spreewald canal network |
—
|
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: Spreewald canal network | Statement: [Raddusch, hasNearbyCanalSystem, Spreewald canal network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCanalSystem Context triple: [Raddusch, hasNearbyCanalSystem, Spreewald canal network]
-
A.
hasCanals
Indicates that one entity possesses or contains canals, either as physical waterways or channel-like structures.
-
B.
nearbyCanal
chosen
Indicates that one entity is located close to or in the immediate vicinity of a canal.
-
C.
hasIndustrialCanalFeatures
Indicates that an entity possesses physical or structural characteristics associated with industrial canals, such as engineered waterways, locks, channels, or related infrastructure used for industrial purposes.
-
D.
hasMajorCanal
Indicates that one entity possesses or contains a primary canal or main waterway associated with it.
-
E.
hasAdjacentCanal
Indicates that one entity is directly next to or alongside a canal.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 12:27 a.m.