Triple
T24781064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лаперу́зов пролив |
E619996
|
entity |
| Predicate | ширинаМаксимальная |
P25021
|
FINISHED |
| Object | около 43 км |
—
|
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: около 43 км | Statement: [Лаперу́зов пролив, ширинаМаксимальная, около 43 км]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ширинаМаксимальная Context triple: [Лаперу́зов пролив, ширинаМаксимальная, около 43 км]
-
A.
maximumChannelWidth
chosen
Indicates the greatest allowable or observed width of a channel in the given context.
-
B.
availableWidth
Indicates the amount of horizontal space that is currently free or usable within a given context or container.
-
C.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
D.
hasMaximumBreadth
Indicates that an entity possesses the greatest breadth (widest extent) among a set of comparable entities or within a defined context.
-
E.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
- 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_69f410d67a208190909034a085b20b59 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:44 a.m.