Triple
T2264408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osage Nation |
E50110
|
entity |
| Predicate | resourceOwnership |
P347
|
FINISHED |
| Object | mineral estate in Osage County, Oklahoma |
—
|
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: mineral estate in Osage County, Oklahoma | Statement: [Osage Nation, resourceOwnership, mineral estate in Osage County, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceOwnership Context triple: [Osage Nation, resourceOwnership, mineral estate in Osage County, Oklahoma]
-
A.
privateOwnershipShare
Indicates the proportion or share of ownership in an entity that is held by private (non-governmental) owners.
-
B.
ownsOrManages
Indicates that one entity has ownership of, or managerial control over, another entity.
-
C.
publicOwnershipShare
Indicates the proportion of an entity that is owned by public shareholders or the general public, as opposed to private or insider ownership.
-
D.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
E.
ownedBy
chosen
Indicates that one entity possesses legal or rightful ownership of 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.