Triple
T824644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Scala |
E17826
|
entity |
| Predicate | openingSeasonTradition |
P16999
|
FINISHED |
| Object | opera season opens on 7 December |
—
|
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: opera season opens on 7 December | Statement: [La Scala, openingSeasonTradition, opera season opens on 7 December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingSeasonTradition Context triple: [La Scala, openingSeasonTradition, opera season opens on 7 December]
-
A.
openSeason
Indicates that a period has begun during which a particular activity (such as hunting, fishing, or competition) is officially allowed or actively underway.
-
B.
inauguralSeason
Indicates the first season in which an entity (such as a team, league, or event) officially began participating or operating.
-
C.
typicalStartSeason
Indicates the season during which something (such as an activity, event, or phenomenon) usually begins.
-
D.
startSeason
chosen
Indicates the point in time or event at which a particular season begins.
-
E.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab7eb0a08190889463edb0e7bd59 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.