Triple
T6549678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renville Agreement |
E151098
|
entity |
| Predicate | negotiationVenueType |
P9722
|
FINISHED |
| Object | U.S. warship |
—
|
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: U.S. warship | Statement: [Renville Agreement, negotiationVenueType, U.S. warship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiationVenueType Context triple: [Renville Agreement, negotiationVenueType, U.S. warship]
-
A.
negotiationLocation
Indicates the place or setting where a negotiation or bargaining process takes or took place.
-
B.
typeOfNegotiation
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
-
C.
negotiationForum
chosen
Indicates that a negotiation or bargaining process takes place within, or is facilitated by, a particular forum, venue, or platform.
-
D.
negotiatedVia
Indicates that an agreement, deal, or arrangement was reached through the use of a specific intermediary, channel, or method of negotiation.
-
E.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.