Triple
T24781065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лаперу́зов пролив |
E619996
|
entity |
| Predicate | ширинаМинимальная |
P12977
|
FINISHED |
| Object | около 40 км |
—
|
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: около 40 км | Statement: [Лаперу́зов пролив, ширинаМинимальная, около 40 км]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ширинаМинимальная Context triple: [Лаперу́зов пролив, ширинаМинимальная, около 40 км]
-
A.
minimumWidth
chosen
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
B.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
C.
minimality
Indicates that something has the smallest or least possible value, size, or complexity among a relevant set, such that no strictly smaller or simpler alternative satisfies the same conditions.
-
D.
minimumSize
Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
-
E.
isNarrowestPartOf
Indicates that one entity constitutes the slimmest or most constricted section within the extent or structure 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:44 a.m.