Triple
T26911522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney Rocketdyne |
E677398
|
entity |
| Predicate | designedEngine |
P65183
|
FINISHED |
| Object | RS-25 |
—
|
NE NERFINISHED |
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: RS-25 | Statement: [Pratt & Whitney Rocketdyne, designedEngine, RS-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedEngine Context triple: [Pratt & Whitney Rocketdyne, designedEngine, RS-25]
-
A.
developedEngine
chosen
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
B.
plannedEngineModel
Indicates that an engine model has been selected or designated as the one intended to be used or implemented in a future plan or configuration.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
originalEngineType
Indicates the type or category of engine that an entity was initially or first equipped with.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 6:02 a.m.