Triple
T411824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tax Court of Canada |
E9504
|
entity |
| Predicate | hearsCasesIn |
P7680
|
FINISHED |
| Object | various cities across Canada |
—
|
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: various cities across Canada | Statement: [Tax Court of Canada, hearsCasesIn, various cities across Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearsCasesIn Context triple: [Tax Court of Canada, hearsCasesIn, various cities across Canada]
-
A.
cannotHearCasesFrom
Indicates that one entity lacks the authority or ability to hear, consider, or adjudicate cases originating from another entity.
-
B.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
C.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
D.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
E.
trialHeldIn
chosen
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecdafa2481908111accc918ff2e8 |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e9749234819084b0ce94faabd0b1 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.