Triple
T34488512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papendrecht |
E885398
|
entity |
| Predicate | hasNeighboringMunicipalityAcrossWater |
P201102
|
FINISHED |
| Object | Dordrecht |
E40368
|
NE 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: Dordrecht | Statement: [Papendrecht, hasNeighboringMunicipalityAcrossWater, Dordrecht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringMunicipalityAcrossWater Context triple: [Papendrecht, hasNeighboringMunicipalityAcrossWater, Dordrecht]
-
A.
borderingCountryAcrossWater
Indicates that one country is geographically separated from another by a body of water yet lies close enough to be considered a neighboring country across that water.
-
B.
hasCoastalMunicipalitiesNeighbor
Indicates that one coastal municipality directly borders or adjoins another coastal municipality.
-
C.
hasNeighboringCantonAcrossLake
Indicates that one canton is directly across a lake from another canton, with the lake forming their mutual boundary.
-
D.
borderingStateAcrossWater
Indicates that one state is adjacent to another with their shared boundary separated by a body of water rather than by land.
-
E.
neighbouringMunicipality
Indicates that one municipality directly borders and is adjacent to another municipality.
- F. None of above. chosen
Provenance (5 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4c6f43c8190a1bc1fbd0c912f78 |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69ffc7b41e688190ad3b86d87c38888e |
completed | May 9, 2026, 11:48 p.m. |
Created at: May 1, 2026, 2:01 a.m.