Triple
T18795929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formerly Utilized Sites Remedial Action Program |
E459633
|
entity |
| Predicate | typeOfContamination |
P24582
|
FINISHED |
| Object | uranium |
—
|
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 | Statement: [Formerly Utilized Sites Remedial Action Program, typeOfContamination, uranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfContamination Context triple: [Formerly Utilized Sites Remedial Action Program, typeOfContamination, uranium]
-
A.
containsContaminant
chosen
Indicates that one entity includes, holds, or is tainted by an unwanted or harmful contaminating substance or element.
-
B.
infectionType
Indicates the specific category or nature of an infection associated with an entity or event.
-
C.
toxinType
Indicates the specific kind or category of toxin associated with an entity.
-
D.
infectionMethod
Indicates the way or mechanism by which an infection is transmitted or established from a source to a host.
-
E.
routeOfExposure
Indicates the pathway or method by which an agent, substance, or factor comes into contact with or enters an organism or system.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01ed3c08190890d9518ed69fdee |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.