Triple
T12212544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanier Cup |
E290999
|
entity |
| Predicate | broadcastOn |
P833
|
FINISHED |
| Object | RDS |
E37965
|
NE 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: RDS | Statement: [Vanier Cup, broadcastOn, RDS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RDS Context triple: [Vanier Cup, broadcastOn, RDS]
-
A.
RDS
chosen
RDS is a Canadian French-language sports television network that broadcasts a wide range of professional and amateur sporting events.
-
B.
RDS
RDS is a Microsoft Windows Server role that enables users to remotely access desktops and applications hosted on centralized servers.
-
C.
RDS2
RDS2 is a Swiss French-language television channel that serves as a secondary sports-focused outlet to the main Réseau des sports (RDS) network.
-
D.
Amazon RDS
Amazon RDS is a managed relational database service by Amazon Web Services that simplifies setup, operation, and scaling of databases in the cloud.
-
E.
ApsaraDB for RDS
ApsaraDB for RDS is Alibaba Cloud’s managed relational database service that provides scalable, high-availability SQL databases with automated management and security features.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91c915f548190b34a743f0a3bb51a |
completed | April 10, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a9f45108190a814cdca52e77b5e |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:51 p.m.