Triple
T23721837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China and North Korea |
E586165
|
entity |
| Predicate | ChineseAllyInKoreanWar |
P153700
|
FINISHED |
| Object | North Korea |
—
|
NE NERFINISHED |
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: North Korea | Statement: [China and North Korea, ChineseAllyInKoreanWar, North Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseAllyInKoreanWar Context triple: [China and North Korea, ChineseAllyInKoreanWar, North Korea]
-
A.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
B.
battleStarsKoreanWar
Indicates that an entity received battle stars for its participation in the Korean War.
-
C.
roleDuringSecondSinoJapaneseWar
Indicates the specific role, position, or function an entity held or performed during the Second Sino-Japanese War.
-
D.
roleAtBattleOfYaluRiver
Indicates the specific role, position, or function an entity held or performed during the Battle of the Yalu River.
-
E.
ChineseCommander
Indicates that an individual holds a commander role within a Chinese military or armed forces context.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91177c08190bea6e62ed13e2495 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:02 p.m.