Triple
T2875785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelly Cup |
E56873
|
entity |
| Predicate | finalSeriesDetermines |
P14140
|
FINISHED |
| Object | Kelly Cup champion |
—
|
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: Kelly Cup champion | Statement: [Kelly Cup, finalSeriesDetermines, Kelly Cup champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSeriesDetermines Context triple: [Kelly Cup, finalSeriesDetermines, Kelly Cup champion]
-
A.
finalSeriesQualifierFor
Indicates that one entity serves as the qualifying event, stage, or condition that determines another entity’s participation in a final series or championship.
-
B.
decidingSeriesResult
chosen
Indicates that an event or action determines the final outcome of a competitive series between parties.
-
C.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
-
D.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
E.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe004a64481908f1897d9054a7368 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.