Triple
T486397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Cup 2001 |
E9887
|
entity |
| Predicate | decidingMatchFor |
P14034
|
FINISHED |
| Object | 2001 MLS season title |
—
|
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: 2001 MLS season title | Statement: [MLS Cup 2001, decidingMatchFor, 2001 MLS season title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingMatchFor Context triple: [MLS Cup 2001, decidingMatchFor, 2001 MLS season title]
-
A.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
B.
decidingGameWinner
Indicates that an event, action, or process determines which participant is the winner of a game.
-
C.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
D.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
E.
decidingGameCity
Indicates the city where the decisive or final game of a series, match, or competition takes place.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0bc6f548190b13dee42cb100423 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.