Triple
T17381040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coeur d'Alene people |
E422566
|
entity |
| Predicate | treatyResultedIn |
P7978
|
FINISHED |
| Object | land cession |
—
|
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 cession | Statement: [Coeur d'Alene people, treatyResultedIn, land cession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyResultedIn Context triple: [Coeur d'Alene people, treatyResultedIn, land cession]
-
A.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
B.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
-
C.
cededByTreaty
chosen
Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
-
D.
hasTreatySettlementWith
Indicates the existence of a formal treaty-based agreement or settlement between two parties.
-
E.
treatyImposed
Indicates that a treaty or formal agreement has been forced upon one party by another, rather than being mutually and voluntarily agreed.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a860f588190915e0671f44bfbcc |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.