Triple
T20572320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seabrook Station Nuclear Power Plant |
E505130
|
entity |
| Predicate | hasIngestionPathwayZoneRadius_miles |
P140614
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [Seabrook Station Nuclear Power Plant, hasIngestionPathwayZoneRadius_miles, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIngestionPathwayZoneRadius_miles Context triple: [Seabrook Station Nuclear Power Plant, hasIngestionPathwayZoneRadius_miles, 50]
-
A.
hasRadiusRange
Indicates that there is a specified minimum and maximum radius within which the related entity or feature falls.
-
B.
evacuationZoneRadius_km
Indicates the distance, in kilometers, from a central point within which people or assets must be evacuated or kept clear.
-
C.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
D.
isRadialRouteOf
Indicates that one route functions as a radial connection extending outward from a central point, hub, or main route.
-
E.
neighborhoodRadius
Indicates the maximum distance around a reference entity within which other entities are considered to be in its neighborhood.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a906f0508190ac698233738f4452 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.