Triple
T5222006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Revolution |
E117889
|
entity |
| Predicate | capitalEvent |
P16721
|
FINISHED |
| Object | seizure of power in Hanoi |
—
|
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: seizure of power in Hanoi | Statement: [August Revolution, capitalEvent, seizure of power in Hanoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalEvent Context triple: [August Revolution, capitalEvent, seizure of power in Hanoi]
-
A.
politicalEvent
chosen
Indicates an occurrence related to political processes, activities, or changes involving governance, power, or public policy.
-
B.
celebratedEvent
Indicates that an entity has been honored, commemorated, or festively observed as a special event.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
commemorativeEvent
Indicates an event held specifically to honor, remember, or mark the significance of a person, group, or past occurrence.
-
E.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7aba05b48190b6a7fc52ab3532f0 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.