Triple
T16120466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graz Opera House |
E391121
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Graz |
E91728
|
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: Graz | Statement: [Graz Opera House, locatedIn, Graz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Graz Context triple: [Graz Opera House, locatedIn, Graz]
-
A.
Graz
chosen
Graz is Austria’s second-largest city, known for its well-preserved medieval old town and historic role as a center of science and education.
-
B.
Villach
Villach is a historic city in southern Austria known for its Alpine setting, thermal spas, and role as a regional transport and cultural hub.
-
C.
Klagenfurt
Klagenfurt is the capital city of the Austrian state of Carinthia, known for its historic old town and proximity to Lake Wörthersee.
-
D.
St. Pölten
St. Pölten is the capital city of the Austrian state of Lower Austria, known for its baroque architecture and role as a regional administrative and cultural center.
-
E.
Linz
Linz is a major Austrian city known for its industrial heritage, vibrant cultural scene, and location along the Danube River.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20200acac8190a47e6a917ff8dd34 |
completed | April 17, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003548837c819091695a91f88bd0bc |
completed | May 10, 2026, 7:35 a.m. |
Created at: April 10, 2026, 5 a.m.