Triple
T18751081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shippingport Atomic Power Station |
E458525
|
entity |
| Predicate | siteReturnedToGreenfield |
P133409
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shippingport Atomic Power Station, siteReturnedToGreenfield, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteReturnedToGreenfield Context triple: [Shippingport Atomic Power Station, siteReturnedToGreenfield, true]
-
A.
siteClearedBy
Indicates that a particular site has been cleared or prepared as a result of actions performed by a specified agent or entity.
-
B.
siteRedevelopedAs
Indicates that a site has been transformed, rebuilt, or repurposed into a new form, function, or development.
-
C.
reopenedOnSiteOf
Indicates that something has been reopened at the same physical location where it previously existed or operated.
-
D.
relocatedToCurrentSite
Indicates that an entity moved from its previous location to the place where it is currently situated.
-
E.
siteNowPartOf
Indicates that one site has become incorporated into or included within another site as part of a current larger whole.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ed4e6881908791f2a6250010a6 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49a9bcc0c81908df3e513fd6762ff |
completed | April 19, 2026, 9:04 a.m. |
Created at: April 10, 2026, 11:51 a.m.