Triple
T19137737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nose (opera production) |
E468475
|
entity |
| Predicate | firstSeasonAtMet |
P106063
|
FINISHED |
| Object | 2009–2010 season |
—
|
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: 2009–2010 season | Statement: [The Nose (opera production), firstSeasonAtMet, 2009–2010 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonAtMet Context triple: [The Nose (opera production), firstSeasonAtMet, 2009–2010 season]
-
A.
firstPerformanceSeason
chosen
Indicates the season in which an entity (such as a work or performer) had its first performance.
-
B.
firstMetInLeague
Indicates that the two entities first met each other within the context of a particular league or league competition.
-
C.
firstMeetingYear
Indicates the calendar year in which two entities first met or had their initial encounter.
-
D.
firstSeasonInTopFlight
Indicates the season in which an entity (typically a team or club) first competed in the highest level of a league or competition.
-
E.
firstYearPlayed
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ee8b988190914ef21ca1b890c6 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.