Triple
T4385473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona Cardinals–Seattle Seahawks rivalry |
E99230
|
entity |
| Predicate | beganRegularDivisionalPlayIn |
P56289
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Arizona Cardinals–Seattle Seahawks rivalry, beganRegularDivisionalPlayIn, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRegularDivisionalPlayIn Context triple: [Arizona Cardinals–Seattle Seahawks rivalry, beganRegularDivisionalPlayIn, 2002]
-
A.
beganInLeagueSeason
Indicates that an entity (such as a team, player, or competition) began its participation or activity during a specified league season.
-
B.
divisionPlayedIn
Indicates that an entity (such as a team or player) participated in or was a member of a particular competitive division.
-
C.
beganPlayBetweenTeams
Indicates that a game or match has started between the specified teams.
-
D.
regularSeasonStart
Indicates the date or point in time when a competition’s regular season officially begins.
-
E.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
- F. None of above. chosen
Provenance (4 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35264e44c81908dd0e0a81f1353bb |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.