Triple
T32312899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Osan |
E825548
|
entity |
| Predicate | NKArmorStrength |
P173959
|
FINISHED |
| Object | approximately 33 T-34 tanks |
—
|
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: approximately 33 T-34 tanks | Statement: [Battle of Osan, NKArmorStrength, approximately 33 T-34 tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NKArmorStrength Context triple: [Battle of Osan, NKArmorStrength, approximately 33 T-34 tanks]
-
A.
armourProtection
Indicates that one entity provides protective armor or defensive covering for another entity.
-
B.
armorProtectionLevel
Indicates the degree or rating of protective capability that armor provides against threats or damage.
-
C.
armourThickness
Indicates the measured thickness of an entity’s protective armor in the context of defense or shielding.
-
D.
hasArmorPlating
Indicates that one entity is equipped with or covered by protective armor plating in relation to another entity or context.
-
E.
armourCoverage
Indicates the extent or area of a subject’s body or structure that is protected or covered by armour.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdb8755481908645da7ceef44e17 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:46 a.m.