Triple
T10231603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omaha Reservation |
E243351
|
entity |
| Predicate | hasTypeOfLandTenure |
P34249
|
FINISHED |
| Object | trust 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: trust land | Statement: [Omaha Reservation, hasTypeOfLandTenure, trust land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfLandTenure Context triple: [Omaha Reservation, hasTypeOfLandTenure, trust land]
-
A.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
B.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
C.
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.
-
D.
hasLandAllotmentDescribedIn
Indicates that an entity’s land allotment is specified or detailed in a particular document or description.
-
E.
seaTenureSystem
Indicates a system governing rights, access, and control over the use and management of marine or sea areas.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:20 a.m.