Triple
T10935448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Шивелуч |
E258320
|
entity |
| Predicate | регионАктивности |
P65106
|
FINISHED |
| Object | Северная часть Камчатской вулканической дуги |
—
|
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: Северная часть Камчатской вулканической дуги | Statement: [Шивелуч, регионАктивности, Северная часть Камчатской вулканической дуги]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: регионАктивности Context triple: [Шивелуч, регионАктивности, Северная часть Камчатской вулканической дуги]
-
A.
регионДеятельности
chosen
Indicates the geographic region or area in which an entity carries out its activities or operations.
-
B.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
C.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
D.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
E.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770aee178819082c1671a37ff7d82 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.