Triple
T9668486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K-27 plant |
E233765
|
entity |
| Predicate | materialHandled |
P28567
|
FINISHED |
| Object | uranium hexafluoride |
—
|
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 hexafluoride | Statement: [K-27 plant, materialHandled, uranium hexafluoride]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialHandled Context triple: [K-27 plant, materialHandled, uranium hexafluoride]
-
A.
materialProvidedFor
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
-
B.
materialInvolved
Indicates that a particular material participates in, is used by, or is otherwise involved in the referenced process, event, or relationship.
-
C.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
materialWorked
Indicates that an agent performs work or processing on a specified material.
-
E.
handlesMaterial
chosen
Indicates that an entity is responsible for managing, processing, or otherwise dealing with a specified material.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3d5b3481908c8c66a3528875aa |
completed | April 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.