Triple

T38035737
Position Surface form Disambiguated ID Type / Status
Subject Rostov Kremlin E949345 entity
Predicate hasBellCollection P11115 FINISHED
Object yes 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: yes | Statement: [Rostov Kremlin, hasBellCollection, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBellCollection
Context triple: [Rostov Kremlin, hasBellCollection, yes]
  • A. hasBells chosen
    Indicates that an entity possesses or is equipped with one or more bells.
  • B. hasBellWeight
    Indicates that an entity (typically a bell) has a specific weight value associated with it.
  • C. hasBellChamber
    Indicates that an entity possesses or includes a bell chamber as one of its structural or functional components.
  • D. hasBellsOrigin
    Indicates that something originates from, or has its source in, bells.
  • E. bellsUsedFor
    Indicates that certain bells are employed or utilized for a particular purpose, function, or activity.
  • 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_69f76eff0bb0819084bc4e63997bd039 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fd67191cf88190b53ecbf5be3564e9 completed May 8, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69fd654fdaac81908e67e75194710f06 completed May 8, 2026, 4:23 a.m.
Created at: May 3, 2026, 4:20 p.m.