Triple
T77605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Peace Accords negotiations on the Vietnam War |
E1551
|
entity |
| Predicate | negotiationFormat |
P130
|
FINISHED |
| Object | four-party talks |
—
|
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: four-party talks | Statement: [Paris Peace Accords negotiations on the Vietnam War, negotiationFormat, four-party talks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiationFormat Context triple: [Paris Peace Accords negotiations on the Vietnam War, negotiationFormat, four-party talks]
-
A.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
B.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
D.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
E.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a2559892dc81909303f2eefdc0025f |
completed | Feb. 28, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69a24eaf99e481908e8d314577e22ecf |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.