Triple
T28170466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. v. Lavell |
E715442
|
entity |
| Predicate | hasLevelOfAppeal |
P71353
|
FINISHED |
| Object | final court of appeal in 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: final court of appeal in Canada | Statement: [R. v. Lavell, hasLevelOfAppeal, final court of appeal in Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelOfAppeal Context triple: [R. v. Lavell, hasLevelOfAppeal, final court of appeal in Canada]
-
A.
levelOfAppeal
Indicates the degree or intensity to which something is attractive, interesting, or desirable to someone or something.
-
B.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
C.
hasMassAppeal
Indicates that something possesses qualities or characteristics that attract or are appealing to a very large, broad, or general audience.
-
D.
hadCourtLevel
chosen
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
E.
hasEnduringAppeal
Indicates that something continues to attract interest, admiration, or enjoyment over a long period of time.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 10:12 p.m.