Triple
T9148591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhytomyr Oblast |
E219523
|
entity |
| Predicate | partlyAffectedBy |
P25489
|
FINISHED |
| Object | Chernobyl disaster fallout |
—
|
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: Chernobyl disaster fallout | Statement: [Zhytomyr Oblast, partlyAffectedBy, Chernobyl disaster fallout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyAffectedBy Context triple: [Zhytomyr Oblast, partlyAffectedBy, Chernobyl disaster fallout]
-
A.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
-
B.
partlyProtectedBy
Indicates that an entity is only partially safeguarded or covered by a specified protective measure, not fully protected.
-
C.
partiallySupportedBy
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
-
D.
partlyControlledBy
Indicates that one entity has partial or limited control or influence over another entity, but not full or exclusive control.
-
E.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca91a1fd08190a5bb3d9280439b09 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.