Triple
T15771272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameco Corporation |
E382365
|
entity |
| Predicate | fuelServicesInclude |
P45008
|
FINISHED |
| Object | uranium conversion |
—
|
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 conversion | Statement: [Cameco Corporation, fuelServicesInclude, uranium conversion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelServicesInclude Context triple: [Cameco Corporation, fuelServicesInclude, uranium conversion]
-
A.
fuelSupplier
Indicates that one entity supplies fuel to another as a provider in a fuel-related relationship.
-
B.
hasFuelServices
chosen
Indicates that one entity provides or is equipped with fuel-related services or facilities for another entity.
-
C.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
D.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
E.
fuelRole
Indicates that one entity serves as the fuel or energy source used or consumed by another entity in a process or operation.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051962fe08190a6201dd48196a9ee |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.