Triple
T7311468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raukkan community |
E168099
|
entity |
| Predicate | hasLandRights |
P34249
|
FINISHED |
| Object | Aboriginal land |
—
|
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 land | Statement: [Raukkan community, hasLandRights, Aboriginal land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandRights Context triple: [Raukkan community, hasLandRights, Aboriginal land]
-
A.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
B.
hasLandOwnershipMix
Indicates that an entity has a particular combination or distribution of different types of land ownership (e.g., public, private, communal) associated with it.
-
C.
hasLandAllotmentDescribedIn
Indicates that an entity’s land allotment is specified or detailed in a particular document or description.
-
D.
hasHistoricLandGrants
Indicates that an entity has been granted land through one or more historically significant official land grants.
-
E.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec00fef081909cb9768a70cabd80 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.