Triple
T36795900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R v Oakes |
E909179
|
entity |
| Predicate | charterSectionInvolved |
P19101
|
FINISHED |
| Object | section 1 |
—
|
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: section 1 | Statement: [R v Oakes, charterSectionInvolved, section 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterSectionInvolved Context triple: [R v Oakes, charterSectionInvolved, section 1]
-
A.
charterSubject
Indicates that an entity is the subject or primary focus of a charter, such as an organization, project, or initiative formally defined or authorized by that charter.
-
B.
charterSecured
Indicates that an official charter or authorization has been successfully obtained or granted for the relevant entity or activity.
-
C.
hasSectionInvolved
chosen
Indicates that a particular section or subdivision is involved or participates in a specified relationship, process, or context.
-
D.
basedOnCharterChapter
Indicates that something is founded, defined, or determined according to a specific chapter of a charter.
-
E.
usesSectionOf
Indicates that one entity makes use of a specific section or part of another entity.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:12 p.m.