Triple
T25765049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Browns shoes |
E648857
|
entity |
| Predicate | seasonalDemandPeak |
P164182
|
FINISHED |
| Object | NFL regular 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: NFL regular season | Statement: [Cleveland Browns shoes, seasonalDemandPeak, NFL regular season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalDemandPeak Context triple: [Cleveland Browns shoes, seasonalDemandPeak, NFL regular season]
-
A.
peakDemandUnit
Indicates the unit of measurement used to express the peak level of demand in a given context.
-
B.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
C.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
D.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
E.
hasSeasonalRidershipPeak
Indicates that the ridership of an entity (such as a service or route) reaches its highest levels during specific seasons or times of the year.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 22, 2026, 5:09 a.m.