Triple
T31019076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkeley Pit |
E790403
|
entity |
| Predicate | designatedAsSuperfund |
P80685
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [Berkeley Pit, designatedAsSuperfund, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsSuperfund Context triple: [Berkeley Pit, designatedAsSuperfund, 1983]
-
A.
addedToSuperfund
Indicates that an entity (typically a site or location) has been officially designated and included in the Superfund program for environmental cleanup or remediation.
-
B.
superfundListingYear
chosen
Indicates the year in which a site was officially placed on the Superfund (National Priorities List) for environmental cleanup.
-
C.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
D.
hasIndustrialSiteIn
Indicates that an entity possesses, operates, or is responsible for an industrial facility located within a specified place or area.
-
E.
USGSDesignation
Indicates that an entity has an official designation or classification assigned by the United States Geological Survey (USGS).
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 29, 2026, 8:58 p.m.