Triple
T32730014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K1A1 |
E836922
|
entity |
| Predicate | replacedArmamentOf |
P71587
|
FINISHED |
| Object | K1 |
—
|
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: K1 | Statement: [K1A1, replacedArmamentOf, K1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedArmamentOf Context triple: [K1A1, replacedArmamentOf, K1]
-
A.
armamentAfterRefit
chosen
Indicates that the armament of an entity reflects its configuration after undergoing a refit or upgrade.
-
B.
enhancedArmament
Indicates that an entity’s weaponry or combat equipment has been upgraded, augmented, or otherwise improved beyond its standard configuration.
-
C.
tertiaryArmament
Indicates the relationship where an entity possesses or is equipped with a third-level (tertiary) weapon or armament beyond its primary and secondary armaments.
-
D.
armamentConfiguration
Indicates how weapons or armaments are arranged, equipped, or configured on an entity in a given context.
-
E.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: May 1, 2026, 1:11 a.m.