Triple
T30447927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tổng Khởi Nghĩa Tháng Tám |
E774631
|
entity |
| Predicate | mởĐầuBằng |
P169446
|
FINISHED |
| Object | khởi nghĩa giành chính quyền ở Hà Nội |
—
|
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: khởi nghĩa giành chính quyền ở Hà Nội | Statement: [Tổng Khởi Nghĩa Tháng Tám, mởĐầuBằng, khởi nghĩa giành chính quyền ở Hà Nội]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mởĐầuBằng Context triple: [Tổng Khởi Nghĩa Tháng Tám, mởĐầuBằng, khởi nghĩa giành chính quyền ở Hà Nội]
-
A.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
-
B.
openedFirstLine
Indicates that one entity initiated the opening of something (e.g., a file, document, or interface) before any other entity did, being the first to perform the opening action.
-
C.
openingDynamic
Indicates that one entity initiates or begins another entity or process in a way that can change or vary over time or context.
-
D.
openingBegan
Indicates that the process of opening something has started.
-
E.
openingVerseBy
Indicates that a work’s opening verse is authored, performed, or otherwise created by the specified entity.
- F. None of above. chosen
Provenance (4 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686c07ac48190b5169557e67861c9 |
completed | May 2, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 8:09 p.m.