Triple
T24201847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernoye volcano |
E600001
|
entity |
| Predicate | monitoringCountry |
P155158
|
FINISHED |
| Object | Russia |
—
|
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: Russia | Statement: [Chernoye volcano, monitoringCountry, Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoringCountry Context triple: [Chernoye volcano, monitoringCountry, Russia]
-
A.
countryMonitored
Indicates that one country is being observed, supervised, or kept under surveillance by another entity or authority.
-
B.
countryStatus
Indicates the political or legal condition of a country, such as its sovereignty, recognition, or current state in international or domestic contexts.
-
C.
countryTargeted
Indicates that a particular country is the intended object or focus of an action, operation, or influence.
-
D.
countryAssessed
Indicates that a particular country has been evaluated or examined according to a specified assessment, criteria, or process.
-
E.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca1f3b481908c14052a8435fd21 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.