Triple
T27803781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ушишир |
E702317
|
entity |
| Predicate | труднодоступенИз-за |
P11058
|
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.
isDifficultToAccessBecauseOf
chosen
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
-
B.
isDifficultToAccess
Indicates that reaching, using, or obtaining the referenced entity requires significant effort, obstacles, or special conditions.
-
C.
tractableOn
Indicates that a problem, task, or situation can be effectively handled, solved, or managed under the specified conditions or by the specified method.
-
D.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
E.
isDifficultToSeeFrom
Indicates that one entity is hard to visually perceive or observe when viewed from the vantage point or location of another entity.
- 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.