Triple
T16256666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regierungsbezirk Mittelfranken |
E394647
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Roth |
E97815
|
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: Roth | Statement: [Regierungsbezirk Mittelfranken, contains, Roth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roth Context triple: [Regierungsbezirk Mittelfranken, contains, Roth]
-
A.
Roth
Roth is a locality within the German town of Lichtenfels in the state of Bavaria.
-
B.
Roth
chosen
Roth is a town in the Bavarian region of Middle Franconia in southern Germany.
-
C.
Roth
Roth is one of the central soldiers in Norman Mailer’s World War II novel "The Naked and the Dead," representing the psychological and moral struggles of men in combat.
-
D.
Roth
Roth is a common German- and Jewish-origin surname borne by numerous notable individuals across literature, politics, science, and the arts.
-
E.
Rothman
Rothman is a surname, often of Jewish or German origin, borne by various notable individuals across fields such as science, business, and the arts.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459b1624819086bf681075097235 |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000ee9bc4c8190bb7e54ed2ad162b3 |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.