Triple
T4143128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRIGA research reactor |
E89319
|
entity |
| Predicate | usesFuelType |
P22119
|
FINISHED |
| Object | uranium-zirconium hydride 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: uranium-zirconium hydride fuel | Statement: [TRIGA research reactor, usesFuelType, uranium-zirconium hydride fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFuelType Context triple: [TRIGA research reactor, usesFuelType, uranium-zirconium hydride fuel]
-
A.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
B.
fuelRole
Indicates that one entity serves as the fuel or energy source used or consumed by another entity in a process or operation.
-
C.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
D.
typicalFuel
chosen
Indicates the kind of fuel that is normally or most commonly used by an entity (such as a device, vehicle, or system).
-
E.
previousFuelType
Indicates that an entity was formerly associated with or used a specified type of fuel before a change to a different fuel type.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.