Triple

T15863207
Position Surface form Disambiguated ID Type / Status
Subject Котлин E384641 entity
Predicate историческиИзвестенКак P1558 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. historicallyRecognizedAs chosen
    Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
  • B. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • C. historicalHeir
    Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
  • D. roleHistoricallyAssociatedWith
    Indicates that one role, position, or function has been historically linked or commonly associated with another entity, role, or context over time.
  • E. historicalNameType
    Indicates that the relationship specifies the type or category of a historical name associated with an 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e174de2cd48190ab18e48c9f051a2a completed April 16, 2026, 11:46 p.m.
PD Predicate disambiguation batch_69e142b976c081908d3ba3e705419f3a completed April 16, 2026, 8:12 p.m.
Created at: April 10, 2026, 4:50 a.m.