Triple
T19867188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaporizhzhia Nuclear Power Plant |
E477419
|
entity |
| Predicate | hasIAEAPresenceSince |
P137633
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Zaporizhzhia Nuclear Power Plant, hasIAEAPresenceSince, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAEAPresenceSince Context triple: [Zaporizhzhia Nuclear Power Plant, hasIAEAPresenceSince, 2022]
-
A.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
B.
hasEvidenceOfActivitySince
Indicates that there is evidence showing an entity has been active or engaged in some activity from a specified point in time onward.
-
C.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
D.
historicalPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
E.
hasLargePresenceIn
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a0a7288190a82b85e3ae056d6b |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.