Triple
T27803769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ушишир |
E702317
|
entity |
| Predicate | покрыт |
P48754
|
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.
surfaceCover
chosen
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
B.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
C.
coverUpBy
Indicates that one entity conceals, suppresses, or hides the actions, information, or wrongdoing associated with another entity.
-
D.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
E.
hasCoverings
Indicates that one entity possesses or is equipped with protective or enclosing layers, surfaces, or coverings provided by 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.