Triple
T22539654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiananmen Square protests of 1989 |
E557252
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | June Fourth Incident |
—
|
NE NERFINISHED |
How this triple was built (3 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: June Fourth Incident | Statement: [Tiananmen Square protests of 1989, alsoKnownAs, June Fourth Incident]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: June Fourth Incident Context triple: [Tiananmen Square protests of 1989, alsoKnownAs, June Fourth Incident]
-
A.
31 March Incident
The 31 March Incident was a 1909 counterrevolutionary uprising in the Ottoman Empire, led by conservative and religious factions in Istanbul against the Young Turk constitutional regime.
-
B.
February 28 Incident
The February 28 Incident was a 1947 anti-government uprising in Taiwan and its brutal suppression by the Kuomintang authorities, marking a pivotal and traumatic event in Taiwanese history.
-
C.
Gwangju Uprising
The Gwangju Uprising was a 1980 pro-democracy revolt in South Korea in which citizens of Gwangju rose up against military dictatorship, becoming a pivotal event in the country’s democratization.
-
D.
January 28 Incident
The January 28 Incident was a 1932 military conflict in Shanghai between Chinese and Japanese forces that marked a major early clash in the lead-up to the Second Sino-Japanese War.
-
E.
May 15 Incident
The May 15 Incident was a 1932 coup attempt in Japan in which young naval officers and right-wing extremists assassinated Prime Minister Inukai Tsuyoshi, marking a major step toward militarist rule.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: June Fourth Incident Target entity description: The June Fourth Incident refers to the Chinese government’s violent suppression of pro-democracy demonstrations in and around Beijing’s Tiananmen Square in early June 1989.
-
A.
31 March Incident
The 31 March Incident was a 1909 counterrevolutionary uprising in the Ottoman Empire, led by conservative and religious factions in Istanbul against the Young Turk constitutional regime.
-
B.
February 28 Incident
The February 28 Incident was a 1947 anti-government uprising in Taiwan and its brutal suppression by the Kuomintang authorities, marking a pivotal and traumatic event in Taiwanese history.
-
C.
Gwangju Uprising
The Gwangju Uprising was a 1980 pro-democracy revolt in South Korea in which citizens of Gwangju rose up against military dictatorship, becoming a pivotal event in the country’s democratization.
-
D.
January 28 Incident
The January 28 Incident was a 1932 military conflict in Shanghai between Chinese and Japanese forces that marked a major early clash in the lead-up to the Second Sino-Japanese War.
-
E.
May 15 Incident
The May 15 Incident was a 1932 coup attempt in Japan in which young naval officers and right-wing extremists assassinated Prime Minister Inukai Tsuyoshi, marking a major step toward militarist rule.
- F. None of above. chosen
Provenance (2 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f3196fc819098deffb0c7932ccc |
completed | April 29, 2026, 1:30 a.m. |
Created at: April 16, 2026, 8:51 p.m.