Triple

T31242371
Position Surface form Disambiguated ID Type / Status
Subject Golitsyno E796595 entity
Predicate isResidentialSatelliteOf P91913 FINISHED
Object Moscow 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: Moscow | Statement: [Golitsyno, isResidentialSatelliteOf, Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isResidentialSatelliteOf
Context triple: [Golitsyno, isResidentialSatelliteOf, Moscow]
  • A. isDistantSatelliteOf
    Indicates that one celestial body orbits another at a relatively large distance, functioning as a far-removed satellite of that primary body.
  • B. isLagrangianSatelliteOf
    Indicates that one celestial body occupies a Lagrangian point and thus functions as a gravitationally bound satellite associated with another primary body.
  • C. isNaturalSatelliteFeatureOf
    Indicates that a physical feature (such as a crater, valley, or mountain) is located on and belongs to a specific natural satellite (e.g., a moon).
  • D. isSatelliteSiteOf chosen
    Indicates that one site functions as a subsidiary, dependent, or secondary location associated with another primary or main site.
  • E. retrievedSatellite
    Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
  • 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_69f224db69ac81909a370adad6a7ac7c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69dfdda708190be290c7bec205445 completed May 3, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f69d1a37e081908d1d86b90ff502bd completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 9:11 p.m.