Triple
T15864797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gatow |
E384682
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Kladow |
E379227
|
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: Kladow | Statement: [Gatow, adjacentTo, Kladow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kladow Context triple: [Gatow, adjacentTo, Kladow]
-
A.
Kladow
chosen
Kladow is a village-like district on the southwestern edge of Berlin, known for its lakeside location on the Havel and its green, suburban character.
-
B.
Klichaw
Klichaw is a small town in eastern Belarus known for its rural character and location within the Mogilev Region.
-
C.
Kabaty
Kabaty is a residential neighborhood in the southern part of Warsaw, Poland, known for its proximity to the Kabaty Forest and as the terminus area of the city’s first metro line.
-
D.
Kladnica
Kladnica is a river that serves as one of the tributaries of the Kolubara in Serbia.
-
E.
Kamienna
Kamienna is a river in south-central Poland that flows through the Świętokrzyskie region before joining the Vistula River.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1555e4ee48190a3b27b4ab9bdb1c8 |
completed | April 16, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa945d9808190a65f5182db341393 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.