Triple
T36347262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Старый Шивелуч |
E895097
|
entity |
| Predicate | типСтруктуры |
P157987
|
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.
типСтроения
Indicates the specific kind or category of building or structure associated with an entity.
-
B.
laterStructureType
Indicates that one structure is of a type that occurs or is instantiated later than another structure in a temporal or sequential sense.
-
C.
structureClass
chosen
Indicates a classification relationship where an entity is assigned to or associated with a particular structural type or category.
-
D.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
E.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.