Triple
T37989096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatro San Moisè |
E947775
|
entity |
| Predicate | activeAsOperaHouseUntil |
P6603
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Teatro San Moisè, activeAsOperaHouseUntil, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeAsOperaHouseUntil Context triple: [Teatro San Moisè, activeAsOperaHouseUntil, early 19th century]
-
A.
activeAsOperaHouseFrom
Indicates that an entity functioned as an opera house starting from a specified point in time.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
operaHouseOfPremiere
Indicates the opera house where a particular work was first premiered or originally performed.
-
D.
reopenedAsOperaHouse
Indicates that a venue or building, previously closed or used differently, was reopened specifically to function as an opera house.
-
E.
hasOperaHouseAssociation
Indicates a relationship where an entity is connected or related to an opera house, such as through location, ownership, operation, affiliation, or significant involvement.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:20 p.m.