Triple
T7961860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hit the Floor |
E184883
|
entity |
| Predicate | season3PremiereDate |
P76933
|
FINISHED |
| Object | 2016-01-18 |
—
|
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: 2016-01-18 | Statement: [Hit the Floor, season3PremiereDate, 2016-01-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: season3PremiereDate Context triple: [Hit the Floor, season3PremiereDate, 2016-01-18]
-
A.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
B.
seasonStartDate
chosen
Indicates the calendar date on which a particular season begins.
-
C.
season3Subject
Indicates that the subject is associated with or pertains to the third season of a series or recurring event.
-
D.
thirdSeasonCoversPeriod
Indicates that the third season of a series or show encompasses or portrays a specific time period or span of events.
-
E.
firstSeasonScheduled
Indicates that the initial season of an entity (such as a show, competition, or event series) has been planned and assigned a schedule.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b8256dc8190a4b73df7aded9097 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:12 p.m.