Triple
T23534827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YK40 |
E576670
|
entity |
| Predicate | appliesToEngineConfiguration |
P72810
|
FINISHED |
| Object | three-engined aircraft |
—
|
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: three-engined aircraft | Statement: [YK40, appliesToEngineConfiguration, three-engined aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToEngineConfiguration Context triple: [YK40, appliesToEngineConfiguration, three-engined aircraft]
-
A.
appliesToConfiguration
chosen
Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
-
B.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
C.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
D.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ae164f348190a6bde1a0dfc66389 |
completed | April 29, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.