Triple
T12205748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZEEP reactor |
E290830
|
entity |
| Predicate | fuelEnrichment |
P103776
|
FINISHED |
| Object | natural (unenriched) uranium |
—
|
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: natural (unenriched) uranium | Statement: [ZEEP reactor, fuelEnrichment, natural (unenriched) uranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelEnrichment Context triple: [ZEEP reactor, fuelEnrichment, natural (unenriched) uranium]
-
A.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
-
B.
hasFuelEnrichmentRange
Indicates that there is a specified range of fuel enrichment levels associated with an entity or relationship.
-
C.
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.
-
D.
fuelEffect
Indicates the influence or impact that a given fuel has on a process, system, or outcome.
-
E.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d920e312708190b4aede2e21f5f697 |
completed | April 10, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69d91c3d669c81908eea7ad61122d275 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d920c3dc9881908c396a4ab34f4836 |
completed | April 10, 2026, 4:09 p.m. |
Created at: April 8, 2026, 9:51 p.m.