Triple
T8574189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Germany |
E203004
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Plauen |
E75799
|
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: Plauen | Statement: [Eastern Germany, contains, Plauen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Plauen Context triple: [Eastern Germany, contains, Plauen]
-
A.
Plauen
chosen
Plauen is a historic town in eastern Germany known for its textile industry and intricate lace production.
-
B.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
C.
Riedholz
Riedholz is a small Swiss municipality located in the canton of Solothurn.
-
D.
Radeberg
Radeberg is a small town in the German state of Saxony, known for its Radeberger Pilsner brewery and historic town center near Dresden.
-
E.
Geringswalde
Geringswalde is a small town in the Free State of Saxony in eastern Germany, known for its rural character and location within the Central Saxon 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea947f188190af469babaa73ddf6 |
completed | March 31, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea88464b88190983e22e70bf38e63 |
completed | April 2, 2026, 5:33 p.m. |
Created at: March 30, 2026, 6:21 p.m.