Triple
T17265754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Обь |
E419121
|
entity |
| Predicate | имеетДельту |
P59084
|
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.
hasDelta
Indicates that there is a change, difference, or deviation between two related states, values, or versions of something.
-
B.
hasDeltaNear
Indicates that one entity has a delta (change or difference) whose value lies within a specified proximity to another entity’s delta.
-
C.
hasDeltaType
Indicates that one entity is associated with a specific type or category of change (delta) relative to another entity or state.
-
D.
deltaAt
Indicates a change or difference in a value, state, or quantity measured at a specific point, time, or condition.
-
E.
formsDeltaIn
chosen
Indicates that one entity creates or shapes a delta landform within or at the mouth of another entity (typically a body of water or region).
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f44ec7c81909a925fc8692b0a6c |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.