Triple
T31979753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kagnew Battalion |
E816543
|
entity |
| Predicate | numberOfDeploymentsToKorea |
P203395
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Kagnew Battalion, numberOfDeploymentsToKorea, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDeploymentsToKorea Context triple: [Kagnew Battalion, numberOfDeploymentsToKorea, 3]
-
A.
sideInKoreanWar
Indicates that an entity participated as a belligerent on a particular side in the Korean War.
-
B.
KoreanCasualties
Indicates that an entity experienced casualties (deaths or injuries) in the context of the Korean War.
-
C.
roleInKoreanWar
Indicates the specific function, position, or involvement an entity had during the Korean War.
-
D.
NorthKoreaDependence
Indicates a relationship where one party relies on or is significantly influenced by North Korea for support, resources, or strategic backing.
-
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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
| PDg | Predicate description generation | batch_6a0174e7e4c88190b8d81c3d78294f94 |
completed | May 11, 2026, 6:19 a.m. |
Created at: May 1, 2026, 12:11 a.m.