Triple
T23012625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-body platform |
E572947
|
entity |
| Predicate | primaryEngineConfiguration |
P141160
|
FINISHED |
| Object | inline-four |
—
|
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: inline-four | Statement: [F-body platform, primaryEngineConfiguration, inline-four]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEngineConfiguration Context triple: [F-body platform, primaryEngineConfiguration, inline-four]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
C.
originalEngineType
chosen
Indicates the type or category of engine that an entity was initially or first equipped with.
-
D.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
E.
coreStageEngineType
Indicates the specific type or model of engine used in the core stage of a launch vehicle or rocket.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e202a481908d7a2f00a12229a0 |
completed | April 29, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.