Triple

T35746034
Position Surface form Disambiguated ID Type / Status
Subject Highland Park, Texas E1033182 entity
Predicate averageHomePriceCharacteristic P9356 FINISHED
Object among highest in Dallas–Fort Worth region 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: among highest in Dallas–Fort Worth region | Statement: [Highland Park, Texas, averageHomePriceCharacteristic, among highest in Dallas–Fort Worth region]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: averageHomePriceCharacteristic
Context triple: [Highland Park, Texas, averageHomePriceCharacteristic, among highest in Dallas–Fort Worth region]
  • A. estateCharacteristic
    Indicates that an estate possesses a particular attribute, quality, or defining feature.
  • B. realEstateMarketCharacteristic
    Indicates a characteristic, condition, or defining feature of a real estate market.
  • C. neighborhoodCharacteristic chosen
    Indicates that a particular characteristic, feature, or quality is associated with or describes a given neighborhood.
  • D. hasHouseCharacteristic
    Indicates that a house possesses or exhibits a specific characteristic, feature, or attribute.
  • E. medianHomeValues
    Indicates the typical (middle) home price or value within a given area or group of properties.
  • 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_69f76e119d508190a3873cb302063832 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c475c58c8190a883554231e88c88 completed May 3, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:06 p.m.