Triple
T5221636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trillium Cup |
E117881
|
entity |
| Predicate | hasRivalryClubFromCountry |
P9795
|
FINISHED |
| Object | Canadian club |
—
|
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: Canadian club | Statement: [Trillium Cup, hasRivalryClubFromCountry, Canadian club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryClubFromCountry Context triple: [Trillium Cup, hasRivalryClubFromCountry, Canadian club]
-
A.
hasForeignRival
chosen
Indicates that an entity has at least one rival that is based in or originates from a different country or foreign jurisdiction.
-
B.
hasClubInCountry
Indicates that a club is located in, based in, or operates within a specified country.
-
C.
hasLocalRivalry
Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
-
D.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
E.
hasHistoricRivalry
Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
- 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.