Triple
T12526566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Hellgate |
E299453
|
entity |
| Predicate | negotiatorRole |
P9269
|
FINISHED |
| Object | Governor of Washington Territory |
—
|
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: Governor of Washington Territory | Statement: [Treaty of Hellgate, negotiatorRole, Governor of Washington Territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiatorRole Context triple: [Treaty of Hellgate, negotiatorRole, Governor of Washington Territory]
-
A.
negotiationRole
chosen
Indicates the specific function or capacity an entity assumes within a negotiation process (e.g., buyer, seller, mediator, or representative).
-
B.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
C.
negotiatingPartyLeader
Indicates that the subject is the primary representative or leader directing or overseeing a party involved in a negotiation.
-
D.
negotiationDirection
Indicates the direction or flow of a negotiation, specifying which party is initiating or driving the negotiation toward the other.
-
E.
negotiation
Indicates a process in which two or more parties communicate and make offers and counteroffers to reach a mutually acceptable agreement.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.