Triple
T28014863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Green Bay Packers season |
E707519
|
entity |
| Predicate | divisionalRoundOpponent |
P164555
|
FINISHED |
| Object | San Francisco 49ers |
—
|
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: San Francisco 49ers | Statement: [2021 Green Bay Packers season, divisionalRoundOpponent, San Francisco 49ers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionalRoundOpponent Context triple: [2021 Green Bay Packers season, divisionalRoundOpponent, San Francisco 49ers]
-
A.
divisionalRoundIncluded
Indicates that the referenced entity includes or pertains to the divisional round stage within a larger competition or playoff structure.
-
B.
NFCDivisionalOpponent
Indicates that one team is an opponent of another within the same NFC division in the NFL.
-
C.
quarterFinalOpponent
Indicates that one entity is the opponent faced by another entity in a quarter-final stage of a competition or tournament.
-
D.
opponentDivision
Indicates that one entity is assigned to or associated with the competitive division of its opponent.
-
E.
divisionMatchup
Indicates a competitive pairing or game scheduled between two entities within the same division.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 8:06 p.m.