Triple
T14763813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikulin AM-38 |
E346940
|
entity |
| Predicate | frontTypeOptimisation |
P115701
|
FINISHED |
| Object | low-altitude performance |
—
|
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: low-altitude performance | Statement: [Mikulin AM-38, frontTypeOptimisation, low-altitude performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontTypeOptimisation Context triple: [Mikulin AM-38, frontTypeOptimisation, low-altitude performance]
-
A.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
B.
frontSightType
Indicates the specific kind or design of the front sight used on an object, typically a firearm or similar aiming device.
-
C.
frontAssignment
Indicates that one entity is assigned or positioned at the front relative to another entity or context.
-
D.
frontDesign
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
-
E.
frontEnginePosition
Indicates that the engine of a vehicle is located at the front portion of the vehicle.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f3a1608190b1b17624003a0c7f |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.