Triple
T17947581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Molson MBA International Case Competition |
E448744
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international case competition |
C6978
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: international case competition Context triple: [John Molson MBA International Case Competition, instanceOf, international case competition]
-
A.
international competition
chosen
An international competition is a structured event in which individuals or teams from multiple countries compete under standardized rules to determine relative excellence in a specific field or activity.
-
B.
international legal case
An international legal case is a formal dispute between states, international organizations, or other cross-border parties that is adjudicated or arbitrated under international law by a recognized international court, tribunal, or dispute-resolution body.
-
C.
international law journal
An international law journal is a scholarly periodical that publishes peer-reviewed articles, case notes, and commentary on legal issues, developments, and theories in public and private international law.
-
D.
case competition club
A case competition club is a student organization that prepares members to analyze real-world business problems and present strategic solutions in competitive, team-based settings.
-
E.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
- F. None of above.
Provenance (1 batch)
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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:21 a.m.