Triple
T25031109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | uranium-235 |
E626843
|
entity |
| Predicate | chemicalFormInFuel |
P11818
|
FINISHED |
| Object | uranium hexafluoride |
—
|
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: uranium hexafluoride | Statement: [uranium-235, chemicalFormInFuel, uranium hexafluoride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chemicalFormInFuel Context triple: [uranium-235, chemicalFormInFuel, uranium hexafluoride]
-
A.
fuelForm
chosen
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
B.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
-
C.
chemicalFormInPET
Indicates the specific chemical form in which a substance is present within a PET (polyethylene terephthalate) material or context.
-
D.
fuelCharacteristic
Indicates a relationship where a fuel is associated with one of its defining properties or qualities, such as composition, performance, or behavior.
-
E.
propellantForm
Indicates the physical or chemical form in which a propellant is present or used in a system.
- 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_69f453035f508190be83a3d521723acf |
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:07 a.m.