Triple
T7785604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boven Merwede |
E187235
|
entity |
| Predicate | separatesNear |
P78999
|
FINISHED |
| Object | Gorinchem |
—
|
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: Gorinchem | Statement: [Boven Merwede, separatesNear, Gorinchem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesNear Context triple: [Boven Merwede, separatesNear, Gorinchem]
-
A.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
B.
separatesAt
Indicates that one entity divides or splits another entity into distinct parts at a specific point, boundary, or location.
-
C.
separatesDirection
Indicates that one entity divides or distinguishes different directions or directional paths from each other.
-
D.
separatesPointsOn
Indicates that one entity divides or partitions a set or space such that distinct points lie on different sides or regions relative to it.
-
E.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
| PDg | Predicate description generation | batch_69cae7e47c5c8190bca90d45b3cdc25e |
completed | March 30, 2026, 9:15 p.m. |
Created at: March 30, 2026, 4:23 p.m.