Triple
T23721839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China and North Korea |
E586165
|
entity |
| Predicate | ChineseInterventionStartYear |
P63012
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [China and North Korea, ChineseInterventionStartYear, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseInterventionStartYear Context triple: [China and North Korea, ChineseInterventionStartYear, 1950]
-
A.
MukdenIncidentYear
Indicates the specific year in which the Mukden Incident occurred.
-
B.
JapaneseOccupationStart
Indicates the point in time when a Japanese occupation of a place or population begins.
-
C.
conflictBeganInYear
Indicates that the specified conflict started or first broke out in the given calendar year.
-
D.
foreignMilitaryInterventionStart
chosen
Indicates the point in time when a foreign state's military forces begin intervening in another state's territory or conflict.
-
E.
armedStruggleStart
Indicates the point in time when an organized group initiates the use of armed force or violence as a method of struggle or conflict.
- 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_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. |
Created at: April 17, 2026, 7:02 p.m.