Triple
T25585302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-14 |
E641362
|
entity |
| Predicate | Mi-14PLRole |
P103357
|
FINISHED |
| Object | anti-submarine warfare |
—
|
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: anti-submarine warfare | Statement: [Mil Mi-14, Mi-14PLRole, anti-submarine warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Mi-14PLRole Context triple: [Mil Mi-14, Mi-14PLRole, anti-submarine warfare]
-
A.
isHelicopterVariantOf
Indicates that one helicopter model is a modified or derived version of another helicopter model.
-
B.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
C.
PZL MielecSpecialization
Indicates a specialization relationship in which PZL Mielec focuses its expertise, production, or primary activities on a particular field, product type, or technological domain.
-
D.
helicopterMass
Indicates the mass associated with a helicopter.
-
E.
poweredAircraftRole
chosen
Indicates the functional role or purpose assigned to a powered (engine-driven) aircraft within an operation or context.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9698c3c8190b93af7d959ecd7c1 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:15 p.m.