Triple
T23599971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tee-Hit-Ton Indians v. United States |
E582723
|
entity |
| Predicate | involvesSubject |
P450
|
FINISHED |
| Object | aboriginal title |
—
|
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 title | Statement: [Tee-Hit-Ton Indians v. United States, involvesSubject, aboriginal title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesSubject Context triple: [Tee-Hit-Ton Indians v. United States, involvesSubject, aboriginal title]
-
A.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
C.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
D.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
E.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
- 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0929c548190bb42621d1131d87f |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:43 p.m.