Triple
T19096393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yak-130 |
E467416
|
entity |
| Predicate | canSimulate |
P39122
|
FINISHED |
| Object | Su-27 family flight characteristics |
—
|
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: Su-27 family flight characteristics | Statement: [Yak-130, canSimulate, Su-27 family flight characteristics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSimulate Context triple: [Yak-130, canSimulate, Su-27 family flight characteristics]
-
A.
hasSimulator
Indicates that one entity provides or is associated with a simulator used to model, emulate, or test the behavior of another entity.
-
B.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
E.
canPerform
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another entity.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e369aeac81908913c21f4c234c8e |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.