Triple

T1780206
Position Surface form Disambiguated ID Type / Status
Subject King City, Oregon E39272 entity
Predicate isPlannedCommunity P32319 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: [King City, Oregon, isPlannedCommunity, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPlannedCommunity
Context triple: [King City, Oregon, isPlannedCommunity, true]
  • A. hasPlannedCommunity
    Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
  • B. isSuburbanCommunity
    Indicates that a community is located in a suburban area, typically characterized by residential neighborhoods situated between urban centers and rural regions.
  • C. isSuburbanCommunityIn
    Indicates that a suburban community is located within or belongs to a specified larger geographic or administrative area.
  • D. isResidentialSuburbOf
    Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
  • E. hasNeighbourhood
    Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
  • F. None of above. chosen

Provenance (4 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_69a88630519c8190a17addd83c4a3ef4 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69ab74dc9d1481908084ef07872a71f8 completed March 7, 2026, 12:44 a.m.
PD Predicate disambiguation batch_69aa61cf3ca881908641fd73ce2f7c9d completed March 6, 2026, 5:10 a.m.
PDg Predicate description generation batch_69ab74db3dbc8190ab256a4e158062b8 completed March 7, 2026, 12:44 a.m.
Created at: March 4, 2026, 7:31 p.m.