Triple
T28170457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. v. Lavell |
E715442
|
entity |
| Predicate | testsInstrument |
P41351
|
FINISHED |
| Object | Canadian Bill of Rights |
—
|
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: Canadian Bill of Rights | Statement: [R. v. Lavell, testsInstrument, Canadian Bill of Rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testsInstrument Context triple: [R. v. Lavell, testsInstrument, Canadian Bill of Rights]
-
A.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
B.
instrumentSuite
chosen
Indicates that an action or process is carried out using a particular set or collection of instruments as its means or tools.
-
C.
typicalInstrumentation
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
D.
hasInstrumentationProvidedBy
Indicates that the instrumentation used in an activity, process, or work is supplied or made available by a specified provider.
-
E.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
- 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_69f64236bd1881908fe73f07a7594dd0 |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:12 p.m.