Triple
T26451743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sukhoi Su-57 |
E665367
|
entity |
| Predicate | plannedEngineModel |
P165352
|
FINISHED |
| Object | Izdeliye 30 |
—
|
NE NERFINISHED |
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: Izdeliye 30 | Statement: [Sukhoi Su-57, plannedEngineModel, Izdeliye 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedEngineModel Context triple: [Sukhoi Su-57, plannedEngineModel, Izdeliye 30]
-
A.
originalEngineModel
Indicates that one engine is the original or initial model from which another engine or engine variant is derived.
-
B.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
C.
plannedPropulsionType
Indicates the type of propulsion system that is intended or scheduled to be used for an object or vehicle.
-
D.
planningModelFor
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
E.
plannedMode
Indicates that a particular mode, method, or state has been intentionally selected or scheduled in advance for use.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 27, 2026, 12:06 a.m.