Triple
T23371989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Матуа |
E593498
|
entity |
| Predicate | являетсяОбъектом |
P110638
|
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.
notableObject
Indicates that an entity is especially significant, famous, or noteworthy as an object in a given context or domain.
-
B.
objet
chosen
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
-
C.
objectUsed
Indicates that one entity is used as a tool, instrument, or resource in performing an action involving another entity.
-
D.
hasObject
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
E.
typicalObjectType
Indicates that something is a common or characteristic type of object typically associated with or involved in another entity or situation.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.