Triple

T5447734
Position Surface form Disambiguated ID Type / Status
Subject Upper Brookville E122289 entity
Predicate isPredominantlyResidential P45165 FINISHED
Object true 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: true | Statement: [Upper Brookville, isPredominantlyResidential, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPredominantlyResidential
Context triple: [Upper Brookville, isPredominantlyResidential, true]
  • 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. isResidentialTown chosen
    Indicates that a town is primarily used or designated for residential living rather than for commercial, industrial, or other primary purposes.
  • C. isSuburbanResidentialArea
    Indicates that a location is primarily a residential neighborhood situated in a suburban (non-urban, non-rural) setting.
  • D. hasResidentialArea
    Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
  • E. isPredominantlyRural
    Indicates that a place or region is characterized mainly by rural features, such as low population density and extensive non-urban land use.
  • 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_69bd4640f52c81909e653ec361f66d76 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd95be329c81908783420cf81b6af5 completed March 20, 2026, 6:45 p.m.
PD Predicate disambiguation batch_69bd919e8d18819098c4af6a015e5cc2 completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:07 p.m.