Triple
T17141659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Focke-Wulf Ta 183 design |
E415978
|
entity |
| Predicate | intendedEngineType |
P126273
|
FINISHED |
| Object | axial-flow turbojet |
—
|
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: axial-flow turbojet | Statement: [Focke-Wulf Ta 183 design, intendedEngineType, axial-flow turbojet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEngineType Context triple: [Focke-Wulf Ta 183 design, intendedEngineType, axial-flow turbojet]
-
A.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
B.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
C.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
D.
hasEngineTypeOnDisplay
Indicates that a particular type of engine is being shown or presented as part of a display or exhibition.
-
E.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
- F. None of above. chosen
Provenance (4 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d5de10819090cbd65661b018d3 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.