Triple
T15112833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molten-Salt Reactor Experiment at Oak Ridge |
E360955
|
entity |
| Predicate | primarySaltComposition |
P6564
|
FINISHED |
| Object | LiF–BeF2–ZrF4–UF4 |
—
|
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: LiF–BeF2–ZrF4–UF4 | Statement: [Molten-Salt Reactor Experiment at Oak Ridge, primarySaltComposition, LiF–BeF2–ZrF4–UF4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySaltComposition Context triple: [Molten-Salt Reactor Experiment at Oak Ridge, primarySaltComposition, LiF–BeF2–ZrF4–UF4]
-
A.
primaryChemicalComponent
chosen
Indicates that one entity is the main or predominant chemical substance composing another entity.
-
B.
typicalSaltContent
Indicates the usual or characteristic amount of salt associated with an entity, such as a food or substance.
-
C.
centralPeakComposition
Indicates the material or mineralogical makeup of a central peak within a larger geological or planetary feature.
-
D.
containsSaltDeposit
Indicates that one entity has or includes a salt deposit within its area, volume, or structure.
-
E.
saltMineType
Indicates the specific kind or classification of a salt mine associated with an 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058d786c8190937c6819255c01bd |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.