Triple
T32212208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle electrical power system |
E822837
|
entity |
| Predicate | fuelCellType |
P174142
|
FINISHED |
| Object | alkaline hydrogen-oxygen fuel cell |
—
|
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: alkaline hydrogen-oxygen fuel cell | Statement: [Space Shuttle electrical power system, fuelCellType, alkaline hydrogen-oxygen fuel cell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelCellType Context triple: [Space Shuttle electrical power system, fuelCellType, alkaline hydrogen-oxygen fuel cell]
-
A.
usedFuelCells
Indicates that an entity employed fuel cells as an energy source or power component in its operation or design.
-
B.
fuelCellIssue
Indicates that there is a problem, malfunction, or abnormal condition affecting a fuel cell or its operation.
-
C.
fuelCycleType
Indicates the type or category of fuel cycle process associated with or applied to an entity.
-
D.
fleetFuelType
Indicates the type of fuel used by a fleet as a whole or by vehicles within that fleet.
-
E.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:37 a.m.