Triple
T32212207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle electrical power system |
E822837
|
entity |
| Predicate | fuelCellManufacturer |
P4022
|
FINISHED |
| Object | Pratt & Whitney |
—
|
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: Pratt & Whitney | Statement: [Space Shuttle electrical power system, fuelCellManufacturer, Pratt & Whitney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelCellManufacturer Context triple: [Space Shuttle electrical power system, fuelCellManufacturer, Pratt & Whitney]
-
A.
powerplantManufacturer
Indicates that one entity is the company or organization responsible for manufacturing or producing the power plant associated with another entity.
-
B.
usedFuelCells
Indicates that an entity employed fuel cells as an energy source or power component in its operation or design.
-
C.
fuelSupplier
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
-
D.
manufacturedBy
chosen
Indicates that an item or product is produced or created by a specific manufacturer or maker.
-
E.
engineeredBy
Indicates that an entity has been designed, created, or developed through the technical work or expertise of another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb9412e8819091bd6ee4a29257b7 |
completed | May 3, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:37 a.m.