Triple
T37885348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orchestra of the Theater an der Wien |
E944979
|
entity |
| Predicate | performsInBuilding |
P110948
|
FINISHED |
| Object | historic theater building |
—
|
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: historic theater building | Statement: [Orchestra of the Theater an der Wien, performsInBuilding, historic theater building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsInBuilding Context triple: [Orchestra of the Theater an der Wien, performsInBuilding, historic theater building]
-
A.
occursInBuilding
Indicates that an event or activity takes place within a specific building.
-
B.
isLocatedInBuilding
Indicates that one entity is physically situated within or inside the structure of a particular building.
-
C.
hostedInBuilding
chosen
Indicates that an event, activity, or service takes place within or is accommodated inside a specific building.
-
D.
appliedToBuilding
Indicates that something (such as a process, treatment, regulation, or attribute) is directed toward, implemented on, or otherwise affects a building.
-
E.
tookPlaceInBuilding
Indicates that an event or action occurred within the physical premises of a specific building.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.