Triple
T37902906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL P.24 (test installations) |
E945465
|
entity |
| Predicate | originalDesignEngineType |
P141160
|
FINISHED |
| Object | air‑cooled radial 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: air‑cooled radial engine | Statement: [PZL P.24 (test installations), originalDesignEngineType, air‑cooled radial engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalDesignEngineType Context triple: [PZL P.24 (test installations), originalDesignEngineType, air‑cooled radial engine]
-
A.
originalEngineType
chosen
Indicates the type or category of engine that an entity was initially or first equipped with.
-
B.
originalEngineModel
Indicates that one engine is the original or initial model from which another engine or engine variant is derived.
-
C.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.