Triple
T28370173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreis Kleve |
E718602
|
entity |
| Predicate | hasBorderWithDutchProvince |
P224
|
FINISHED |
| Object | Gelderland |
—
|
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: Gelderland | Statement: [Kreis Kleve, hasBorderWithDutchProvince, Gelderland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderWithDutchProvince Context triple: [Kreis Kleve, hasBorderWithDutchProvince, Gelderland]
-
A.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
-
B.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
isBorderDistrict
Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
-
D.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
-
E.
hasBorderWithinCountry
Indicates that one region or area shares an internal boundary with another region or area within the same country.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.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, 12:59 a.m.