Triple
T11787305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-83 |
E280302
|
entity |
| Predicate | fuelCellIssue |
P101582
|
FINISHED |
| Object | malfunction in one of three fuel cells |
—
|
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: malfunction in one of three fuel cells | Statement: [STS-83, fuelCellIssue, malfunction in one of three fuel cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelCellIssue Context triple: [STS-83, fuelCellIssue, malfunction in one of three fuel cells]
-
A.
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.
-
B.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
C.
fuelCycleFeature
Indicates a characteristic, attribute, or aspect associated with a nuclear fuel cycle process or stage.
-
D.
usesMOXFuel
Indicates that an entity employs mixed-oxide (MOX) fuel as its fuel source or in its operation.
-
E.
fuelEffect
Indicates the influence or impact that a given fuel has on a process, system, or outcome.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a586803481909af0032c35ca6e51 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.