Triple
T34624714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-12 Defensive Player of the Year |
E889102
|
entity |
| Predicate | conferenceNameChangeTo |
P184355
|
FINISHED |
| Object | Pac-12 Conference |
—
|
NE NERFINISHED |
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: Pac-12 Conference | Statement: [Pac-12 Defensive Player of the Year, conferenceNameChangeTo, Pac-12 Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceNameChangeTo Context triple: [Pac-12 Defensive Player of the Year, conferenceNameChangeTo, Pac-12 Conference]
-
A.
conferenceChange
Indicates a change in some aspect of a conference, such as its schedule, location, participants, or configuration.
-
B.
conferenceChangeContext
Indicates a change in the state, scope, or parameters of a conference-related interaction or session.
-
C.
changesNameTo
Indicates that an entity alters its current name and adopts a new specified name.
-
D.
laterConferenceName
chosen
Indicates that one conference is known by a different name at a later time than its original or earlier name.
-
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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 2:04 a.m.