Triple
T29115836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theaterplatz (Dresden) |
E737041
|
entity |
| Predicate | notableBuildingOnSquare |
P57645
|
FINISHED |
| Object | Semperoper |
E197905
|
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: Semperoper | Statement: [Theaterplatz (Dresden), notableBuildingOnSquare, Semperoper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBuildingOnSquare Context triple: [Theaterplatz (Dresden), notableBuildingOnSquare, Semperoper]
-
A.
mainReligiousBuildingOnSquare
Indicates that a religious building serves as the primary or most significant religious structure located on a particular square.
-
B.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
C.
religiousBuildingOnSquare
Indicates that a religious building is located on or directly adjacent to a public square.
-
D.
notableBuildingAssociated
chosen
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
E.
notableBuildingOnStreet
Indicates that a building is notable or significant and is located on a particular street.
- F. None of above.
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25a83ffd0881908f9e47189b74c306 |
completed | June 7, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: April 28, 2026, 11:22 a.m.