Triple
T34286325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Joseph |
E879749
|
entity |
| Predicate | positionOnTreaties |
P143080
|
FINISHED |
| Object | rejected cession of Wallowa Valley lands |
—
|
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: rejected cession of Wallowa Valley lands | Statement: [Old Joseph, positionOnTreaties, rejected cession of Wallowa Valley lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnTreaties Context triple: [Old Joseph, positionOnTreaties, rejected cession of Wallowa Valley lands]
-
A.
positionOnSecurityTreaty
Indicates the stance or viewpoint an entity holds regarding a specific security treaty.
-
B.
roleInTreaties
Indicates the specific capacity, function, or position an entity holds within the context of one or more treaties.
-
C.
stanceOnTreaties
chosen
Indicates the position, attitude, or policy an entity holds regarding specific treaties or treaty-related issues.
-
D.
resultOfTreaties
Indicates that something exists, occurs, or holds true as a consequence or outcome of one or more treaties.
-
E.
treatyFocus
Indicates that a treaty is primarily concerned with, directed toward, or centered on a particular subject, issue, or area.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:57 a.m.