Triple
T14074712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast Mode |
E338701
|
entity |
| Predicate | popularizedInSeason |
P2352
|
FINISHED |
| Object | 2010 NFL season |
—
|
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: 2010 NFL season | Statement: [Beast Mode, popularizedInSeason, 2010 NFL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularizedInSeason Context triple: [Beast Mode, popularizedInSeason, 2010 NFL season]
-
A.
isPopularInSeason
Indicates that something tends to be widely favored, used, or in high demand during a particular season.
-
B.
popularizedIn
chosen
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
C.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
D.
announcedInSeason
Indicates that something (such as a product, feature, or event) was officially announced during a particular season.
-
E.
isPopularSeason
Indicates that a particular season is widely liked, favored, or enjoyed by many people.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.