Triple
T17790447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Nassau-Idstein |
E444144
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Idstein |
—
|
NE NERFINISHED |
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: Idstein | Statement: [House of Nassau-Idstein, locatedIn, Idstein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Idstein Context triple: [House of Nassau-Idstein, locatedIn, Idstein]
-
A.
Idstein
chosen
Idstein is a historic town in the German state of Hesse, known for its well-preserved medieval old town and timber-framed architecture.
-
B.
Stollberg
Stollberg is a historic town in Saxony, Germany, known for its role in the Ore Mountains mining region and its traditional mining heritage.
-
C.
Dornstadt
Dornstadt is a municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, located near the city of Ulm.
-
D.
Planegg
Planegg is a municipality in the district of Munich in Bavaria, Germany, known for its scenic location along the Würm River and its proximity to the city of Munich.
-
E.
Neustettin
Neustettin is a historic town in Pomerania, now known as Szczecinek in northwestern Poland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879688908190a5428b1fa7525f62 |
completed | April 19, 2026, 7:43 a.m. |
Created at: April 10, 2026, 10:13 a.m.