Triple
T34458464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-12 men's basketball season |
E884566
|
entity |
| Predicate | conferenceNameChangeYear |
P1742
|
FINISHED |
| Object | 2011–12 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: 2011–12 season | Statement: [Pac-12 men's basketball season, conferenceNameChangeYear, 2011–12 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceNameChangeYear Context triple: [Pac-12 men's basketball season, conferenceNameChangeYear, 2011–12 season]
-
A.
renamedYear
chosen
Indicates the year in which an entity underwent a renaming or change of name.
-
B.
conferenceChange
Indicates a change in some aspect of a conference, such as its schedule, location, participants, or configuration.
-
C.
conferenceYear
Indicates the specific calendar year in which a given conference takes place or is held.
-
D.
namingRightsChangeYear
Indicates the year in which the naming rights for something (such as a venue, event, or asset) were changed from one name or sponsor to another.
-
E.
coMainEventTitleChange
Indicates a change in the title of a co-main event within a larger event or program.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 2 a.m.