Triple
T36791469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Cup |
E909063
|
entity |
| Predicate | alsoContestedInCountry |
P28246
|
FINISHED |
| Object | Canada |
—
|
NE NERFINISHED |
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: Canada | Statement: [Colonial Cup, alsoContestedInCountry, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoContestedInCountry Context triple: [Colonial Cup, alsoContestedInCountry, Canada]
-
A.
alsoContestedIn
chosen
Indicates that the same issue, claim, or matter is being disputed or challenged in another context, case, or proceeding as well.
-
B.
areContestedIn
Indicates that something is the subject of dispute, challenge, or competition within a particular context, event, or process.
-
C.
countryContestedBy
Indicates that control, ownership, or sovereignty over a country is disputed by multiple parties or entities.
-
D.
qualificationPlacesContested
Indicates the number of positions or spots that are being competed for in a qualification process.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.