Triple
T12057549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 孫基禎 |
E287080
|
entity |
| Predicate | reasonForCompetingForJapan |
P102985
|
FINISHED |
| Object | Japanese colonial rule over Korea |
—
|
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: Japanese colonial rule over Korea | Statement: [孫基禎, reasonForCompetingForJapan, Japanese colonial rule over Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCompetingForJapan Context triple: [孫基禎, reasonForCompetingForJapan, Japanese colonial rule over Korea]
-
A.
objectiveOfJapaneseForces
Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
-
B.
reasonForAttack
Indicates that one entity’s attack on another is motivated or caused by the specified reason.
-
C.
goalDuringWar
Indicates that a particular goal or objective is pursued, exists, or is relevant during the time period of a war or armed conflict.
-
D.
strategicReason
Indicates that one entity serves as a reason, justification, or motivation for another entity’s strategic decision, plan, or action.
-
E.
madeMultipleAttemptsToReachJapan
Indicates that the subject tried to travel to or arrive in Japan on more than one separate occasion.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.