Triple
T17052935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borne |
E413746
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Tubbergen |
E413749
|
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: Tubbergen | Statement: [Borne, borders, Tubbergen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tubbergen Context triple: [Borne, borders, Tubbergen]
-
A.
Tubbergen
chosen
Tubbergen is a rural municipality and village in the eastern Netherlands, located in the Twente region of the province of Overijssel.
-
B.
Zwanenburgwal
Zwanenburgwal is a historic canal and street in central Amsterdam, known for its picturesque views and cultural significance.
-
C.
Schwansen
Schwansen is a rural peninsula in northern Germany situated between the Schlei inlet and the Eckernförde Bay in the state of Schleswig-Holstein.
-
D.
Eemster
Eemster is a small village in the Dutch province of Drenthe, situated within the municipality of Westerveld.
-
E.
Ederveen
Ederveen is a village in the Dutch province of Gelderland, known for its rural character and location within the municipality of Ede.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa491008190ad013ee37532aa51 |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139f346f0819094a430a11e361bac |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:34 a.m.