Triple
T460954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native Americans |
E7334
|
entity |
| Predicate | rightsIssue |
P4517
|
FINISHED |
| Object | land rights |
—
|
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: land rights | Statement: [Native Americans, rightsIssue, land rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsIssue Context triple: [Native Americans, rightsIssue, land rights]
-
A.
rights
Indicates that an entity possesses entitlements, permissions, or legal/moral claims in relation to another entity or context.
-
B.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
C.
concernsRight
chosen
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
D.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
E.
rightHolder
Indicates that one entity holds or possesses a legal or contractual right in relation to another entity or resource.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbed5b88190a45716812eb4cfdf |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.