Triple
T17529053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main-Taunus-Kreis |
E426880
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Flörsheim am Main |
—
|
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: Flörsheim am Main | Statement: [Main-Taunus-Kreis, containsTown, Flörsheim am Main]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flörsheim am Main Context triple: [Main-Taunus-Kreis, containsTown, Flörsheim am Main]
-
A.
Flörsheim am Main
chosen
Flörsheim am Main is a town in the Main-Taunus district of Hesse, Germany, situated on the River Main between Frankfurt and Mainz.
-
B.
Wörth am Main
Wörth am Main is a small town in the Miltenberg district of Bavaria, Germany, situated on the River Main and known for its picturesque riverside setting.
-
C.
Stockstadt am Main
Stockstadt am Main is a market town in the Bavarian district of Aschaffenburg in Germany, situated on the river Main.
-
D.
Zeil am Main
Zeil am Main is a small historic town in northern Bavaria, Germany, known for its wine culture and location along the Main River.
-
E.
Rödelheim
Rödelheim is a district of Frankfurt am Main, Germany, known as a largely residential area with good transport links and local amenities.
- 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d81a808190ab38831ea5b73b74 |
completed | April 19, 2026, 3:58 a.m. |
Created at: April 10, 2026, 5:49 a.m.