Triple
T26804092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2024 |
E671179
|
entity |
| Predicate | hasPreviousEdition |
P193703
|
FINISHED |
| Object | MLS Cup 2023 |
—
|
NE NERFINISHED |
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: MLS Cup 2023 | Statement: [MLS Cup 2024, hasPreviousEdition, MLS Cup 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreviousEdition Context triple: [MLS Cup 2024, hasPreviousEdition, MLS Cup 2023]
-
A.
hasEditionIn
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
B.
presentedSinceEdition
Indicates that something has been continuously presented, featured, or included starting from a specified edition onward.
-
C.
isAnnualEditionOf
Indicates that one entity is a specific yearly edition or version of another, typically recurring publication or event.
-
D.
hasEditionRelationship
Indicates a relationship where one resource is an edition or version of another, linking different manifestations of essentially the same work.
-
E.
hasEditionStatus
Indicates the specific publication or release status assigned to an edition of a work.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: April 27, 2026, 4:25 a.m.