Triple
T9560159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Mile Island Unit 1 |
E230650
|
entity |
| Predicate | permanentlyShutDown |
P11821
|
FINISHED |
| Object | September 20, 2019 |
—
|
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: September 20, 2019 | Statement: [Three Mile Island Unit 1, permanentlyShutDown, September 20, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentlyShutDown Context triple: [Three Mile Island Unit 1, permanentlyShutDown, September 20, 2019]
-
A.
permanentShutdown
chosen
Indicates that an entity has been irreversibly taken out of operation and will not be restarted or resumed in the future.
-
B.
shutdownCapability
Indicates the ability or permission for one entity to power off, deactivate, or terminate the operation of another entity or system.
-
C.
firstLongShutdown
Indicates the first occurrence of a prolonged shutdown event affecting the referenced entity or system.
-
D.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
E.
secondLongShutdown
Indicates that an entity undergoes a second extended or prolonged shutdown event in a sequence of shutdowns.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994bde0c8190afcba5cb8fa8b984 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.