Triple
T31016618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Futaba District |
E790340
|
entity |
| Predicate | hasNuclearFacilityNearby |
P103461
|
FINISHED |
| Object | Fukushima Daiichi Nuclear Power Plant |
—
|
NE NERFINISHED |
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: Fukushima Daiichi Nuclear Power Plant | Statement: [Futaba District, hasNuclearFacilityNearby, Fukushima Daiichi Nuclear Power Plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNuclearFacilityNearby Context triple: [Futaba District, hasNuclearFacilityNearby, Fukushima Daiichi Nuclear Power Plant]
-
A.
hasNuclearPowerPlantNearby
chosen
Indicates that an entity is located close to at least one nuclear power plant.
-
B.
isNuclearSite
Indicates that a location or facility is used for nuclear-related activities, such as power generation, research, weapons development, or radioactive material storage.
-
C.
hadNuclearFacilities
Indicates that an entity possessed or operated nuclear-related installations or infrastructure.
-
D.
hasNuclearReactor
Indicates that an entity possesses, contains, or is equipped with a nuclear reactor.
-
E.
hasNuclearActivity
Indicates that an entity engages in, is involved with, or possesses capabilities related to nuclear activities or operations.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 29, 2026, 8:57 p.m.