Triple
T3205286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2020 |
E67146
|
entity |
| Predicate | attendanceRestrictionReason |
P46152
|
FINISHED |
| Object | COVID-19 pandemic |
—
|
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: COVID-19 pandemic | Statement: [MLS Cup 2020, attendanceRestrictionReason, COVID-19 pandemic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendanceRestrictionReason Context triple: [MLS Cup 2020, attendanceRestrictionReason, COVID-19 pandemic]
-
A.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
B.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
C.
reasonForNonParticipation
Indicates the explanation or cause for why an entity did not take part in a specified activity or event.
-
D.
reasonForDisqualification
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
-
E.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.