Triple
T22149466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fernald uranium plant |
E547375
|
entity |
| Predicate | operationsEnded |
P86578
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Fernald uranium plant, operationsEnded, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationsEnded Context triple: [Fernald uranium plant, operationsEnded, 1989]
-
A.
operationalStatusAtEnd
chosen
Indicates the final operational condition or state of an entity at the conclusion of a specified period or process.
-
B.
alsoEnded
Indicates that one event or state concluded in addition to another already mentioned event or state.
-
C.
deploymentEnd
Indicates the point in time or event at which a deployment process or deployment state comes to an end.
-
D.
developmentEnded
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
-
E.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f2c0e881909c3488bb5eb5959d |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.