Triple
T15005460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darumbal People Native Title Claim (QUD6131/1998) |
E377698
|
entity |
| Predicate | legalRightType |
P5038
|
FINISHED |
| Object | native title |
—
|
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: native title | Statement: [Darumbal People Native Title Claim (QUD6131/1998), legalRightType, native title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRightType Context triple: [Darumbal People Native Title Claim (QUD6131/1998), legalRightType, native title]
-
A.
legalAuthorityType
Indicates the specific kind or category of legal authority that governs, authorizes, or regulates an entity or action.
-
B.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
C.
legalDocumentRelatedToRights
Indicates a relationship where a legal document concerns, defines, or affects the rights or entitlements of entities involved.
-
D.
typeOfRight
chosen
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
-
E.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7322b5c81909089cbbf816e1436 |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.