Triple
T17619463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmand Treaty |
E429669
|
entity |
| Predicate | effectOnVietnam |
P72410
|
FINISHED |
| Object | reduction of Vietnamese sovereignty |
—
|
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: reduction of Vietnamese sovereignty | Statement: [Harmand Treaty, effectOnVietnam, reduction of Vietnamese sovereignty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnVietnam Context triple: [Harmand Treaty, effectOnVietnam, reduction of Vietnamese sovereignty]
-
A.
impactOnVietnam
chosen
Indicates a relationship where one entity has an effect, influence, or consequence on Vietnam.
-
B.
statusAfterVietnamWar
Indicates the condition or situation of an entity following the end of the Vietnam War.
-
C.
positionOnVietnamWar
Indicates a person or entity’s stance, opinion, or policy position regarding the Vietnam War.
-
D.
effectOnUnitedStates
Indicates the impact, influence, or consequences that something has on the United States.
-
E.
estimatedNorthVietnameseCasualties
Indicates the reported or calculated number of casualties attributed to North Vietnamese forces in a given context or event.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3547d88190ae3c9ffed63133c9 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.