Triple
T22435686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höchster Schlossfest |
E554616
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Höchst |
—
|
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: Höchst | Statement: [Höchster Schlossfest, locatedIn, Höchst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Höchst Context triple: [Höchster Schlossfest, locatedIn, Höchst]
-
A.
Höchst
chosen
Höchst is a historic district in western Frankfurt am Main, Germany, known for its well-preserved old town and former industrial and chemical industry sites.
-
B.
Höchst
Höchst is a municipality in the Austrian state of Vorarlberg, located near the Swiss border along the Rhine River.
-
C.
Nassau-Idstein
Nassau-Idstein was a small early modern German state within the Holy Roman Empire, governed by a cadet branch of the House of Nassau.
-
D.
Poppenbüttel
Poppenbüttel is a residential quarter in the borough of Wandsbek in Hamburg, Germany, known for its suburban character and green surroundings.
-
E.
Konstadt
Konstadt is the historical German name for the Polish town of Wołczyn in the Opole Voivodeship.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15adda0e48190825a5b705ae52d5b |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 16, 2026, 8:47 p.m.