Triple

T18720634
Position Surface form Disambiguated ID Type / Status
Subject City of Belvedere E457763 entity
Predicate hasHighMedianHomePrice P99362 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: [City of Belvedere, hasHighMedianHomePrice, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHighMedianHomePrice
Context triple: [City of Belvedere, hasHighMedianHomePrice, true]
  • A. medianHouseholdIncomeHighRelativeTo
    Indicates that the median household income of one entity is significantly higher compared to that of another specified reference entity or benchmark.
  • B. medianHomeValues
    Indicates the typical (middle) home price or value within a given area or group of properties.
  • C. medianHouseholdIncome
    Indicates the typical (middle) value of income earned by households in a given area, such that half of households earn more and half earn less.
  • D. hasHighCostOfLiving chosen
    Indicates that the place or context is associated with expenses for goods, services, or daily life that are significantly higher than average.
  • E. medianHomeValueRank
    Indicates the relative position of a home's value compared to other homes, typically ordered from lowest to highest within a defined group or area.
  • 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_69d8d393ba9c8190a8b03b04ddbb0a09 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56ab9e0dc8190bf579d7e89e941f4 completed April 19, 2026, 11:52 p.m.
PD Predicate disambiguation batch_69e478e0889c8190a118d67b200ce8ef completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:50 a.m.