Triple
T21913277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Major League Soccer season |
E541116
|
entity |
| Predicate | playoffsBeginDate |
P31045
|
FINISHED |
| Object | 2019-10-19 |
—
|
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: 2019-10-19 | Statement: [2019 Major League Soccer season, playoffsBeginDate, 2019-10-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffsBeginDate Context triple: [2019 Major League Soccer season, playoffsBeginDate, 2019-10-19]
-
A.
playoffsStartDate
chosen
Indicates the calendar date on which a competition’s playoff phase begins.
-
B.
playoffsDetermine
Indicates that the outcome of playoff competitions decides or establishes a particular result, status, or ranking between the involved entities.
-
C.
playoffsStatus
Indicates the current stage or outcome of an entity’s participation in a playoff competition (e.g., qualified, in progress, eliminated, or champion).
-
D.
postseasonEnd
Indicates the point in time or event at which a sports league’s postseason (playoffs) concludes.
-
E.
playoffMeetingsEra
Indicates that two entities have faced each other in playoff competition during a specified historical era or time period.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123359e1c8190a606a92c5bcb58e8 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:41 p.m.