Triple
T405476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC East |
E9373
|
entity |
| Predicate | notableTeamDominance |
P5897
|
FINISHED |
| Object | New England Patriots 2001–2019 |
—
|
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: New England Patriots 2001–2019 | Statement: [AFC East, notableTeamDominance, New England Patriots 2001–2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeamDominance Context triple: [AFC East, notableTeamDominance, New England Patriots 2001–2019]
-
A.
notableTeamSeason
Indicates that a particular sports season is especially significant or noteworthy in the history of a given team.
-
B.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
C.
notableSeason
Indicates that a particular season is especially significant or noteworthy in relation to an entity (such as a person, team, or series).
-
D.
historicallyDominantIn
chosen
Indicates that one entity has held a position of prevailing power, influence, or control over another entity or within a particular domain during a past historical period.
-
E.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.