Triple
T2446840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nlaka'pamux |
E53612
|
entity |
| Predicate | treatyStatus |
P38540
|
FINISHED |
| Object | largely without historic treaties |
—
|
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: largely without historic treaties | Statement: [Nlaka'pamux, treatyStatus, largely without historic treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyStatus Context triple: [Nlaka'pamux, treatyStatus, largely without historic treaties]
-
A.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
B.
treatyType
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
-
C.
treatyFocus
Indicates that a treaty is primarily concerned with, directed toward, or centered on a particular subject, issue, or area.
-
D.
treatyEffect
Indicates that a treaty produces a specific legal, political, or practical consequence or change in the relationship between the involved parties.
-
E.
treatyRevisionOutcome
Indicates the result or consequence of a process to revise or amend a treaty.
- F. None of above. chosen
Provenance (4 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_69ab495d227c8190b26ae6548eeb1019 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
| PDg | Predicate description generation | batch_69abcabe646c8190855d13b5dff07b97 |
completed | March 7, 2026, 6:50 a.m. |
Created at: March 6, 2026, 9:43 p.m.