Triple
T3504591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paducah Gaseous Diffusion Plant |
E74044
|
entity |
| Predicate | processGas |
P35806
|
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: [Paducah Gaseous Diffusion Plant, processGas, uranium hexafluoride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processGas Context triple: [Paducah Gaseous Diffusion Plant, processGas, uranium hexafluoride]
-
A.
gasSystem
Indicates a relationship where an entity functions as, is part of, or is associated with a gas-based system used for distribution, control, or processing of gases.
-
B.
typeOfGasUsed
chosen
Indicates the specific kind of gas that is utilized in relation to an entity or process.
-
C.
gasReleased
Indicates that a gas is emitted or discharged from a source into its surrounding environment.
-
D.
gasContent
Indicates that one entity has, contains, or is characterized by a certain amount or type of gas.
-
E.
propellantFeedGas
Indicates a relationship where a gas is used or supplied as the propellant feed in a propulsion or thruster 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbf22b1c8190956141d8fb924210 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.