Triple

T26023544
Position Surface form Disambiguated ID Type / Status
Subject Lyubensk E647218 entity
Predicate hasNameInContext P34621 FINISHED
Object Lyubensk, near Saint Petersburg, Russian Empire NE NERFINISHED

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: Lyubensk, near Saint Petersburg, Russian Empire | Statement: [Lyubensk, hasNameInContext, Lyubensk, near Saint Petersburg, Russian Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNameInContext
Context triple: [Lyubensk, hasNameInContext, Lyubensk, near Saint Petersburg, Russian Empire]
  • A. hasCurrentNameContext
    Indicates that an entity is associated with the name it currently uses or is recognized by in the present context.
  • B. namedInContextOf chosen
    Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
  • C. hasNameDayContext
    Indicates that an entity’s name day is interpreted or celebrated within a specific contextual framework (such as culture, calendar system, or tradition).
  • D. hasNameInNotation
    Indicates that an entity is referred to by a specific name or label within a particular notation or symbolic system.
  • E. isKnownInContextOf
    Indicates that an entity is recognized, relevant, or has significance specifically within a given context or domain.
  • 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_69e77e8b60e88190a3b26c4f0032a2c2 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f6978fe97081908fe568091ad9b159 completed May 3, 2026, 12:32 a.m.
PD Predicate disambiguation batch_69f69661e6ec8190948251c7516a32ad completed May 3, 2026, 12:27 a.m.
Created at: April 22, 2026, 9:05 a.m.