Triple
T22629364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vietnamese communism |
E558505
|
entity |
| Predicate | postReformPeriod |
P10613
|
FINISHED |
| Object | Đổi Mới reforms from 1986 |
—
|
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: Đổi Mới reforms from 1986 | Statement: [Vietnamese communism, postReformPeriod, Đổi Mới reforms from 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postReformPeriod Context triple: [Vietnamese communism, postReformPeriod, Đổi Mới reforms from 1986]
-
A.
postReformDevelopment
chosen
Indicates the development or changes that occur after a reform has been implemented.
-
B.
scriptAfterReform
Indicates that one script or writing system is used after a reform or modification has been applied to another script.
-
C.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
D.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
E.
lastReform
Indicates the most recent reform or change that was applied to an entity, typically linking the entity to its latest reform event or version.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3febd081909ff21abef1e4035d |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.