Triple
T338233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F Reactor |
E6774
|
entity |
| Predicate | cleanupProgram |
P11567
|
FINISHED |
| Object | Hanford Site environmental remediation |
—
|
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: Hanford Site environmental remediation | Statement: [F Reactor, cleanupProgram, Hanford Site environmental remediation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleanupProgram Context triple: [F Reactor, cleanupProgram, Hanford Site environmental remediation]
-
A.
cleanupContractor
Indicates that an entity serves as the contractor responsible for performing cleanup activities for another entity or project.
-
B.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
C.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
programmeName
Indicates that an entity has or is identified by a specific programme’s name.
- F. None of above. chosen
Provenance (4 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae23b0c819081f8bf9ac26685ab |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.