Triple
T4639237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F Area Tank Farm |
E101610
|
entity |
| Predicate | handlesMaterialType |
P28567
|
FINISHED |
| Object | liquid radioactive waste |
—
|
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: liquid radioactive waste | Statement: [F Area Tank Farm, handlesMaterialType, liquid radioactive waste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesMaterialType Context triple: [F Area Tank Farm, handlesMaterialType, liquid radioactive waste]
-
A.
handlesMaterial
chosen
Indicates that an entity is responsible for managing, processing, or otherwise dealing with a specified material.
-
B.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
C.
organizesMaterialType
Indicates that one entity arranges or structures another entity according to a specific type or category of material.
-
D.
sourceMaterialType
Indicates the type or category of material from which something originates or is derived.
-
E.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8e0ee88190becab97d2ef1571a |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.