Triple
T24673854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukita Hideie |
E610920
|
entity |
| Predicate | sideInKoreanWar |
P156952
|
FINISHED |
| Object | Japanese forces |
—
|
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 forces | Statement: [Ukita Hideie, sideInKoreanWar, Japanese forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInKoreanWar Context triple: [Ukita Hideie, sideInKoreanWar, Japanese forces]
-
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.
KoreanCasualties
Indicates that an entity experienced casualties (deaths or injuries) in the context of the Korean War.
-
D.
ChineseAllyInKoreanWar
Indicates that one entity was an ally of China during the Korean War.
-
E.
higherCommandDuringKoreanWar
Indicates that one entity served as the superior command authority over another entity during the Korean War.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:53 a.m.