Triple

T23953053
Position Surface form Disambiguated ID Type / Status
Subject Шхара E603101 entity
Predicate имеетКоординаты P10142 FINISHED
Object примерно 43.0° с.ш., 43.0° в.д. 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.0° с.ш., 43.0° в.д. | Statement: [Шхара, имеетКоординаты, примерно 43.0° с.ш., 43.0° в.д.]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: имеетКоординаты
Context triple: [Шхара, имеетКоординаты, примерно 43.0° с.ш., 43.0° в.д.]
  • A. hasCoordinates chosen
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • B. hasCoordinatesType
    Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
  • C. hasCoordinateRole
    Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
  • D. coordinatesWith
    Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
  • E. coordinates
    Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
  • 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_69e2953e4924819093f1c24c03476b42 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d0d558748190a51b5732a3e6713c completed April 29, 2026, 9:35 a.m.
PD Predicate disambiguation batch_69f1615518088190a206f54e2fdb14a3 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:21 p.m.