Triple
T14029336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 MLS Supporters' Shield |
E337545
|
entity |
| Predicate | tiebreakersInclude |
P6631
|
FINISHED |
| Object | goal difference |
—
|
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: goal difference | Statement: [2018 MLS Supporters' Shield, tiebreakersInclude, goal difference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tiebreakersInclude Context triple: [2018 MLS Supporters' Shield, tiebreakersInclude, goal difference]
-
A.
tiebreaker
chosen
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
B.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
-
C.
fairPlayTiebreakerAffectedTeams
Indicates that the teams involved were impacted by a tiebreaker decision based on fair play criteria (such as disciplinary records).
-
D.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
E.
tieGameReason
Indicates that the specified factor or event is the reason why a particular game or match ended in a tie.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa9f8248190930954d609dee5f1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.