Triple
T3504601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paducah Gaseous Diffusion Plant |
E74044
|
entity |
| Predicate | enrichmentMethod |
P27477
|
FINISHED |
| Object | gaseous diffusion cascade |
—
|
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: gaseous diffusion cascade | Statement: [Paducah Gaseous Diffusion Plant, enrichmentMethod, gaseous diffusion cascade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enrichmentMethod Context triple: [Paducah Gaseous Diffusion Plant, enrichmentMethod, gaseous diffusion cascade]
-
A.
usedEnrichmentMethod
chosen
Indicates that a particular enrichment method was applied or utilized in relation to an entity or process.
-
B.
enrichmentFacility
Indicates a facility where a substance, typically a material or resource, is processed to increase its concentration, quality, or value.
-
C.
featuresMethod
Indicates that an entity includes or provides a particular method as part of its functionality or behavior.
-
D.
discoveryMethod
Indicates the process, technique, or approach by which something was found, detected, or identified.
-
E.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result 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_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.