Triple
T5221628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trillium Cup |
E117881
|
entity |
| Predicate | trophyForDerby |
P2890
|
FINISHED |
| Object | Toronto FC vs Columbus Crew |
—
|
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: Toronto FC vs Columbus Crew | Statement: [Trillium Cup, trophyForDerby, Toronto FC vs Columbus Crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyForDerby Context triple: [Trillium Cup, trophyForDerby, Toronto FC vs Columbus Crew]
-
A.
commemorativeTrophy
Indicates that a trophy exists to honor or memorialize a particular person, event, or achievement.
-
B.
trophy
chosen
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
C.
trophyOfficialName
Indicates the official, formally recognized name assigned to a particular trophy.
-
D.
trophySponsor
Indicates that a sponsor provides financial or material support specifically for a trophy associated with an event, competition, or award.
-
E.
trophyColor
Indicates the color attribute assigned to a trophy in the relationship.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7aba05b48190b6a7fc52ab3532f0 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.