Triple
T23218526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurpfalz |
E580817
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Frankenthal |
—
|
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: Frankenthal | Statement: [Kurpfalz, hasCity, Frankenthal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Frankenthal Context triple: [Kurpfalz, hasCity, Frankenthal]
-
A.
Frankenthal
chosen
Frankenthal is a town in the Rhineland-Palatinate region of southwestern Germany, historically known as a center for art and culture in the late 16th and early 17th centuries.
-
B.
Frankenthal
Frankenthal is a small town located within the Bautzen district in the Free State of Saxony in eastern Germany.
-
C.
Morbach
Morbach is a small town in the Hunsrück region of Rhineland-Palatinate in western Germany, known for its scenic forests and rural landscapes.
-
D.
Passenheim
Passenheim is the former German name of the town now known as Pasym, located in northeastern Poland’s historic region of Masuria.
-
E.
Bruchsal
Bruchsal is a town in the state of Baden-Württemberg in southwestern Germany, known for its baroque palace and asparagus cultivation.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916653f08190a7dcbc659c6b6a25 |
completed | April 29, 2026, 5:04 a.m. |
Created at: April 17, 2026, 4:08 p.m.