Triple
T30488612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 25ID |
E775794
|
entity |
| Predicate | koreanWarParticipation |
P13112
|
FINISHED |
| Object | Korean Peninsula |
—
|
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: Korean Peninsula | Statement: [25ID, koreanWarParticipation, Korean Peninsula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: koreanWarParticipation Context triple: [25ID, koreanWarParticipation, Korean Peninsula]
-
A.
sideInKoreanWar
Indicates that an entity participated as a belligerent on a particular side in the Korean War.
-
B.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
C.
KoreanCasualties
Indicates that an entity experienced casualties (deaths or injuries) in the context of the Korean War.
-
D.
warParticipatedIn
chosen
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
E.
battleStarsKoreanWar
Indicates that an entity received battle stars for its participation in the Korean War.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68747d5cc8190a6b1f934b4dd7fa3 |
completed | May 2, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:13 p.m.