Triple
T6755400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großer Döllnsee |
E154443
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Templin |
E339134
|
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: Templin | Statement: [Großer Döllnsee, locatedNear, Templin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Templin Context triple: [Großer Döllnsee, locatedNear, Templin]
-
A.
Templin
chosen
Templin is a historic spa town in northeastern Germany, known for its medieval city walls and scenic location amid lakes and forests.
-
B.
Bergneustadt
Bergneustadt is a small town in North Rhine-Westphalia, Germany, known for its location in the hilly Oberbergischer Kreis region and its traditional half-timbered architecture.
-
C.
Shingletown
Shingletown is a small rural community in Northern California known for its forested setting near Lassen Volcanic National Park.
-
D.
Carlswald
Carlswald is a residential and commercial suburb located in the Midrand area between Johannesburg and Pretoria in South Africa.
-
E.
Rosettenville
Rosettenville is a residential suburb in the south of Johannesburg, South Africa, known for its diverse community and historical religious and educational institutions.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1f465388190858207ca4c48f18d |
completed | March 27, 2026, 6:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70b1e477481909e4fca040f4894f4 |
completed | March 27, 2026, 10:56 p.m. |
Created at: March 27, 2026, 2:11 p.m.