Triple
T3841285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Orleans Saints–Tampa Bay Buccaneers rivalry |
E93454
|
entity |
| Predicate | beganPlayAgainstEachOther |
P39323
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [New Orleans Saints–Tampa Bay Buccaneers rivalry, beganPlayAgainstEachOther, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPlayAgainstEachOther Context triple: [New Orleans Saints–Tampa Bay Buccaneers rivalry, beganPlayAgainstEachOther, 1977]
-
A.
beganPlayBetweenTeams
chosen
Indicates that a game or match has started between the specified teams.
-
B.
beganCompetition
Indicates that an entity initiated or started participating in a competitive event or contest involving others.
-
C.
sawOpponentsAs
Indicates perceiving or regarding certain entities as opponents or adversaries.
-
D.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
E.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.