Triple
T26592011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sicangu Oyate |
E667382
|
entity |
| Predicate | partOfTreatyHistoryWith |
P45144
|
FINISHED |
| Object | United States government |
—
|
NE NERFINISHED |
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: United States government | Statement: [Sicangu Oyate, partOfTreatyHistoryWith, United States government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfTreatyHistoryWith Context triple: [Sicangu Oyate, partOfTreatyHistoryWith, United States government]
-
A.
treatyHistoryWith
chosen
Indicates a historical record of treaties or formal agreements that have existed between the related entities.
-
B.
historicalTreaty
Indicates that a formal agreement or pact was established between entities at some point in the past.
-
C.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
D.
treatySignedWith
Indicates that a formal treaty or agreement has been officially signed between two parties.
-
E.
treatyMention
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 2:08 a.m.