Triple
T10950269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schmidt Theater |
E258706
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Schmidt Tivoli |
E258707
|
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: Schmidt Tivoli | Statement: [Schmidt Theater, adjacentTo, Schmidt Tivoli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schmidt Tivoli Context triple: [Schmidt Theater, adjacentTo, Schmidt Tivoli]
-
A.
Schmidt Tivoli
chosen
Schmidt Tivoli is a well-known theater and cabaret venue in Hamburg, Germany, famed for its variety shows and musical productions.
-
B.
Tivoli
Tivoli is an Italian hill town east of Rome renowned for its historic villas and gardens, including Emperor Hadrian’s vast imperial retreat, Hadrian’s Villa.
-
C.
Tivoli
Tivoli is an IBM software brand known for its enterprise systems management and monitoring solutions.
-
D.
Schmidt Tivoli GmbH & Co. KG
Schmidt Tivoli GmbH & Co. KG is the company that manages and produces entertainment programs for the renowned Schmidt Theater in Hamburg, Germany.
-
E.
Tivoli Park
Tivoli Park is the largest and most famous public park in Ljubljana, Slovenia, known for its landscaped gardens, walking paths, and cultural venues.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ed2f1c819081ec58457f57889d |
completed | April 9, 2026, 9:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d733f7d88190b45df5c155ff5a46 |
completed | April 18, 2026, 12:58 a.m. |
Created at: April 8, 2026, 9:23 p.m.