Triple
T11617896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klimov VK-1 |
E275555
|
entity |
| Predicate | ChineseDesignation |
P100621
|
FINISHED |
| Object | WP-5 |
—
|
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: WP-5 | Statement: [Klimov VK-1, ChineseDesignation, WP-5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChineseDesignation Context triple: [Klimov VK-1, ChineseDesignation, WP-5]
-
A.
internationalDesignation
Indicates that an entity has been assigned a formal status, code, or recognition by an international body or under an internationally agreed system.
-
B.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
C.
americanDesignation
Indicates that one entity is the official American name, title, or designation for another entity.
-
D.
manufacturerDesignation
Indicates that a specific designation, code, or model identifier has been assigned by the manufacturer to the referenced product or item.
-
E.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a047758081908191c1d564409d9a |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.