Triple
T31884379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermal Oxide Reprocessing Plant |
E813967
|
entity |
| Predicate | fuelTypeReprocessed |
P172690
|
FINISHED |
| Object | thermal oxide fuel |
—
|
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: thermal oxide fuel | Statement: [Thermal Oxide Reprocessing Plant, fuelTypeReprocessed, thermal oxide fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTypeReprocessed Context triple: [Thermal Oxide Reprocessing Plant, fuelTypeReprocessed, thermal oxide fuel]
-
A.
fuelTypeProduced
Indicates the type of fuel that is generated or produced by a given source, process, or facility.
-
B.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in time.
-
C.
usedFusionFuel
Indicates that an entity employed a specified material or substance as fuel in a fusion process.
-
D.
secondaryFuel
Indicates that an entity uses or is associated with a secondary (additional or backup) fuel source in addition to its primary fuel.
-
E.
fuelCycleType
Indicates the type or category of fuel cycle process associated with or applied to an entity.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d99fe08190897822f9b6406e11 |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:57 p.m.