Triple

T5019848
Position Surface form Disambiguated ID Type / Status
Subject Krasnogorsk E112823 entity
Predicate hasResidentialRole P45165 FINISHED
Object commuter town for Moscow 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: commuter town for Moscow | Statement: [Krasnogorsk, hasResidentialRole, commuter town for Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasResidentialRole
Context triple: [Krasnogorsk, hasResidentialRole, commuter town for Moscow]
  • A. isResidential
    Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
  • B. hasResidentialArea
    Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
  • C. isResidentialTown chosen
    Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
  • D. hasResidentialRequirement
    Indicates that an entity is subject to a condition requiring residence in a specified place or under specified living arrangements.
  • E. hasNonHumanResident
    Indicates that a place or location is inhabited or occupied by one or more non-human entities.
  • 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_69bd4435c2f48190be593158cbfcf8a3 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7342c62881909acb35849da8761c completed March 20, 2026, 4:18 p.m.
PD Predicate disambiguation batch_69bd714ecfe08190b5830cfc1c74fa17 completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:36 p.m.