Triple
T25609819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Alexei Navalny poisoning |
E642016
|
entity |
| Predicate | locationOnsetOfSymptoms |
P181722
|
FINISHED |
| Object | flight from Tomsk to Moscow |
—
|
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: flight from Tomsk to Moscow | Statement: [2020 Alexei Navalny poisoning, locationOnsetOfSymptoms, flight from Tomsk to Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnsetOfSymptoms Context triple: [2020 Alexei Navalny poisoning, locationOnsetOfSymptoms, flight from Tomsk to Moscow]
-
A.
typicalOnsetLocation
Indicates the anatomical location where a condition, symptom, or process most commonly begins or first appears.
-
B.
locationOfSeizure
Indicates the place or setting where a seizure event occurs.
-
C.
createdAtLocation
Indicates the place or location where an entity was originally created or brought into existence.
-
D.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
E.
hasOnset
Indicates the point in time or condition at which a process, event, or state begins.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 21, 2026, 4:40 p.m.