Triple
T18434223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. v. Sparrow |
E450349
|
entity |
| Predicate | typeOfRightInvolved |
P5038
|
FINISHED |
| Object | Aboriginal right |
—
|
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: Aboriginal right | Statement: [R. v. Sparrow, typeOfRightInvolved, Aboriginal right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRightInvolved Context triple: [R. v. Sparrow, typeOfRightInvolved, Aboriginal right]
-
A.
rightInvolved
Indicates that an entity is involved in or associated with a legal or formal right held, exercised, or affected in a given context.
-
B.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
C.
typeOfRight
chosen
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
-
D.
typeOfInvolvement
Indicates the specific role, capacity, or manner in which one entity is involved with or participates in another entity or activity.
-
E.
involvedSide
Indicates that an entity participates as one of the parties or sides involved in a particular event, interaction, or situation.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b1915d88190a1ecd81cd78ee7d2 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:28 a.m.