Triple
T24468305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klimov |
E617032
|
entity |
| Predicate | productsUsedIn |
P156215
|
FINISHED |
| Object | military aviation |
—
|
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: military aviation | Statement: [Klimov, productsUsedIn, military aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productsUsedIn Context triple: [Klimov, productsUsedIn, military aviation]
-
A.
usesProduct
Indicates that one entity makes use of, applies, or employs a particular product.
-
B.
usesProductFrom
Indicates that one entity makes use of or employs a product that originates from or is provided by another entity.
-
C.
usedForProduct
Indicates that one entity serves as a tool, component, or means specifically employed in the creation, operation, or delivery of another entity considered as a product.
-
D.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
E.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299413ea88190b15e482035ff5a83 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.