Triple
T36358533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Ministry Specification B.9/32 |
E895417
|
entity |
| Predicate | engineConfigurationRequired |
P38289
|
FINISHED |
| Object | twin‑engined |
—
|
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‑engined | Statement: [Air Ministry Specification B.9/32, engineConfigurationRequired, twin‑engined]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineConfigurationRequired Context triple: [Air Ministry Specification B.9/32, engineConfigurationRequired, twin‑engined]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
combustionEngineConfiguration
Indicates the specific arrangement and setup of components and operating parameters within a combustion engine.
-
C.
requiresConfiguration
chosen
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
D.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
E.
engineBase
Indicates that one entity serves as the foundational or primary engine upon which another engine or engine-related component is built or derived.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.