Triple
T13113861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panketal |
E311041
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Zepernick |
E1021835
|
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: Zepernick | Statement: [Panketal, hasSettlement, Zepernick]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zepernick Context triple: [Panketal, hasSettlement, Zepernick]
-
A.
Zepernick
chosen
Zepernick is a locality in the German state of Brandenburg that now forms part of the municipality of Panketal.
-
B.
Zernien
Zernien is a municipality in Lower Saxony, Germany, situated within the collective municipality (Samtgemeinde) of Elbtalaue.
-
C.
Leppe
Leppe is a small river in western Germany that flows through the hilly Bergisches Land region of North Rhine-Westphalia.
-
D.
Zehdenick
Zehdenick is a small town in the German state of Brandenburg, known for its historic center and location along the Havel River.
-
E.
Talbach
Talbach is a small stream in Switzerland that serves as a tributary of the Ergolz River in the Basel-Landschaft region.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817f8ee8819084078b4bec5e4f18 |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6eadcd7048190aa740262679e5bab |
completed | May 3, 2026, 6:27 a.m. |
Created at: April 9, 2026, 9:06 p.m.