Triple
T36358508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Suitcase |
E895416
|
entity |
| Predicate | refersToEngineConfiguration |
P72810
|
FINISHED |
| Object | twin-engine |
—
|
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: twin-engine | Statement: [Flying Suitcase, refersToEngineConfiguration, twin-engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToEngineConfiguration Context triple: [Flying Suitcase, refersToEngineConfiguration, twin-engine]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
C.
appliesToConfiguration
chosen
Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
-
D.
combustionEngineConfiguration
Indicates the specific arrangement and setup of components and operating parameters within a combustion engine.
-
E.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:09 p.m.