Triple
T9945035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOE-RL |
E195182
|
entity |
| Predicate | usesContractors |
P7138
|
FINISHED |
| Object | prime contractors for Hanford Site cleanup work |
—
|
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: prime contractors for Hanford Site cleanup work | Statement: [DOE-RL, usesContractors, prime contractors for Hanford Site cleanup work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesContractors Context triple: [DOE-RL, usesContractors, prime contractors for Hanford Site cleanup work]
-
A.
employedApproximately
Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
-
B.
primaryContractor
chosen
Indicates that one entity serves as the main responsible contractor for a project, agreement, or work in relation to another entity.
-
C.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
D.
employedSystem
Indicates that a system is used or operated in the context of an employment or work-related arrangement.
-
E.
hasEmployees
Indicates that one entity employs one or more other entities as its workers or staff.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb61561848190aba7250f3b3c4ed5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.