Triple

T30862518
Position Surface form Disambiguated ID Type / Status
Subject Oberwaltersdorf E786098 entity
Predicate hasNotableResidentialArea P9064 FINISHED
Object Fontana residential estate 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: Fontana residential estate | Statement: [Oberwaltersdorf, hasNotableResidentialArea, Fontana residential estate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableResidentialArea
Context triple: [Oberwaltersdorf, hasNotableResidentialArea, Fontana residential estate]
  • A. hasResidentialArea chosen
    Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
  • B. hasNotableNatureArea
    Indicates that an entity possesses or is associated with a significant or noteworthy natural area.
  • C. hasResidentialBuilding
    Indicates that an entity possesses, contains, or is associated with a residential building as part of its properties or components.
  • D. hasQuietResidentialAreas
    Indicates that a place includes neighborhoods characterized by low noise levels and a calm, residential atmosphere.
  • E. hasUpscaleResidentialArea
    Indicates that a location contains or is associated with a high-end, affluent residential neighborhood or district.
  • 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_69f224b91c14819084e764832fe67a57 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_6a0062e6bd788190a7b4f3e5befb5cbb completed May 10, 2026, 10:50 a.m.
PD Predicate disambiguation batch_6a0061989d188190b4815b2de3e8676f completed May 10, 2026, 10:44 a.m.
Created at: April 29, 2026, 8:47 p.m.