Triple
T15597829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSU–Alabama football rivalry |
E374951
|
entity |
| Predicate | oftenScheduledAs |
P55062
|
FINISHED |
| Object | prime-time game |
—
|
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: prime-time game | Statement: [LSU–Alabama football rivalry, oftenScheduledAs, prime-time game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenScheduledAs Context triple: [LSU–Alabama football rivalry, oftenScheduledAs, prime-time game]
-
A.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
B.
scheduledAs
chosen
Indicates that one entity is assigned or arranged to occur or function in the role, time, or capacity specified by another entity within a schedule.
-
C.
scheduledAfter
Indicates that one event or action is planned to occur later in time than another in a defined schedule or sequence.
-
D.
requiresSchedule
Indicates that an entity must have a planned schedule or timetable established before it can occur, operate, or be fulfilled.
-
E.
scheduledInYear
Indicates that an event, activity, or item is planned or set to occur within a specific calendar year.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e609ab081909feb486a57439960 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.