Triple
T1004234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic Republic of Vietnam |
E21671
|
entity |
| Predicate | achievedUnification |
P4318
|
FINISHED |
| Object | 1975-04-30 |
—
|
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: 1975-04-30 | Statement: [Democratic Republic of Vietnam, achievedUnification, 1975-04-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedUnification Context triple: [Democratic Republic of Vietnam, achievedUnification, 1975-04-30]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
-
C.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
D.
unificationDate
chosen
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
E.
admittedToUnionAs
Indicates that an entity (typically a state or region) was formally accepted and incorporated into a political union or federation in a specified capacity or status.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4ff614081909478500ada1f5059 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b1f4f88190822598cfd2a0fd2b |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.