Triple
T25038391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Jets Ltd |
E627042
|
entity |
| Predicate | developedEngineForAircraft |
P65183
|
FINISHED |
| Object | Gloster E.28/39 |
—
|
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: Gloster E.28/39 | Statement: [Power Jets Ltd, developedEngineForAircraft, Gloster E.28/39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedEngineForAircraft Context triple: [Power Jets Ltd, developedEngineForAircraft, Gloster E.28/39]
-
A.
developedEngine
chosen
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
B.
aircraftEngineTypeProduced
Indicates that a particular type of aircraft engine is manufactured or produced by a specified entity.
-
C.
developedAircraft
Indicates that an entity (such as a person or organization) was responsible for designing, creating, or engineering a particular aircraft.
-
D.
aircraftEngineType
Indicates the specific type or classification of engine that an aircraft uses.
-
E.
aircraftPowerplantType
Indicates the type or category of powerplant (e.g., engine or propulsion system) used by an aircraft.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f45308d3148190bc24a7cdb570e866 |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:08 a.m.