Triple
T17396607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2024 MLS Supporters' Shield |
E422969
|
entity |
| Predicate | inceptionOfEdition |
P127318
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [2024 MLS Supporters' Shield, inceptionOfEdition, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionOfEdition Context triple: [2024 MLS Supporters' Shield, inceptionOfEdition, 2024]
-
A.
firstEditionEndYear
Indicates the year in which the first edition of something (such as a work, event, or series) concluded or ceased to be current.
-
B.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
C.
firstCollectedEditionYear
Indicates the year in which the first collected edition of a work was published or made available.
-
D.
firstTypicalEditionYear
Indicates the year in which the first typical or standard edition of a work was published or officially issued.
-
E.
firstRecordedEditionYear
Indicates the calendar year in which the first recorded edition of a work was published or documented.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abd9b748190bd55c863276d9e3a |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.