Triple
T37331713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomeroi Native Title Applicant |
E926767
|
entity |
| Predicate | hasRightClaimed |
P31301
|
FINISHED |
| Object | rights to occupy traditional lands |
—
|
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: rights to occupy traditional lands | Statement: [Gomeroi Native Title Applicant, hasRightClaimed, rights to occupy traditional lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightClaimed Context triple: [Gomeroi Native Title Applicant, hasRightClaimed, rights to occupy traditional lands]
-
A.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
-
B.
hasCollectiveRightClaim
Indicates that a group or collective entity asserts or holds a right or entitlement on behalf of its members.
-
C.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
-
D.
claimedRight
chosen
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
E.
roleClaimed
Indicates that an entity asserts or designates a specific role or position for itself or 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:16 p.m.