Triple
T4761350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aboriginal peoples under the Constitution Act, 1982 |
E105704
|
entity |
| Predicate | includesRightsType |
P5038
|
FINISHED |
| Object | Aboriginal rights |
—
|
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 rights | Statement: [Aboriginal peoples under the Constitution Act, 1982, includesRightsType, Aboriginal rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRightsType Context triple: [Aboriginal peoples under the Constitution Act, 1982, includesRightsType, Aboriginal rights]
-
A.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
B.
typeOfRight
chosen
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
-
C.
incorporatedRightsFrom
Indicates that one entity has absorbed, adopted, or integrated legal rights or entitlements that originally belonged to another entity.
-
D.
rightsStatementType
Indicates the specific category or nature of a rights statement that applies to a resource or entity.
-
E.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.