Triple
T27803764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ушишир |
E702317
|
entity |
| Predicate | имеетОбъект |
P5510
|
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.
hasObject
chosen
Indicates that an entity is associated with or possesses a particular object as part of a relationship or action.
-
B.
containsObjectsBeyond
Indicates that a container or space holds additional objects beyond a specified set, limit, or boundary.
-
C.
objet
Indicates that one entity is the object (recipient or target) of an action or relation performed by another entity.
-
D.
objectUsed
Indicates that one entity is used as a tool, instrument, or resource in performing an action involving another entity.
-
E.
hasObjectSystem
Indicates that something is associated with, contains, or is part of a particular object system.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63838b520819099c7ac2fe66fefb7 |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:36 p.m.