Triple
T36796451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piasecki H-21 Shawnee (re‑engined variants) |
E909195
|
entity |
| Predicate | replacesEngineType |
P196922
|
FINISHED |
| Object | radial piston 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: radial piston engine | Statement: [Piasecki H-21 Shawnee (re‑engined variants), replacesEngineType, radial piston engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesEngineType Context triple: [Piasecki H-21 Shawnee (re‑engined variants), replacesEngineType, radial piston engine]
-
A.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
intendedEngineType
Indicates that an entity is designed or specified to use a particular type of engine.
-
D.
renderingEngineReplacedBy
Indicates that one rendering engine has been superseded or substituted by another rendering engine.
-
E.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
| PDg | Predicate description generation | batch_69fe6e4801108190a6be6bec2d52a1b9 |
completed | May 8, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:12 p.m.