Triple
T34732433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metallener Saal |
E1001248
|
entity |
| Predicate | hasAddressBuilding |
P4379
|
FINISHED |
| Object | Musikvereinsgebäude, Musikvereinsplatz 1, 1010 Wien |
—
|
LITERAL 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: Musikvereinsgebäude, Musikvereinsplatz 1, 1010 Wien | Statement: [Metallener Saal, hasAddressBuilding, Musikvereinsgebäude, Musikvereinsplatz 1, 1010 Wien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressBuilding Context triple: [Metallener Saal, hasAddressBuilding, Musikvereinsgebäude, Musikvereinsplatz 1, 1010 Wien]
-
A.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
B.
hasBuildingLocation
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
C.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
D.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
E.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
- F. None of above.
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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 3:59 p.m.