Triple
T26804093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2024 |
E671179
|
entity |
| Predicate | hasNextEdition |
P2686
|
FINISHED |
| Object | MLS Cup 2025 |
—
|
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 2025 | Statement: [MLS Cup 2024, hasNextEdition, MLS Cup 2025]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNextEdition Context triple: [MLS Cup 2024, hasNextEdition, MLS Cup 2025]
-
A.
nextEdition
chosen
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
-
B.
laterEditionContains
Indicates that a later edition of a work includes all or part of the content from an earlier edition.
-
C.
majorEditionsPlanned
Indicates that significant future versions or releases of an entity (such as a work, product, or publication) are scheduled or intended to be produced.
-
D.
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).
-
E.
hasEditionAvailability
Indicates that a particular edition of an item is available in a specified form, location, or channel.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 4:25 a.m.