Triple

T7975999
Position Surface form Disambiguated ID Type / Status
Subject Ave Maria, Florida E185446 entity
Predicate hasPlannedTownCenter P23364 FINISHED
Object yes 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: yes | Statement: [Ave Maria, Florida, hasPlannedTownCenter, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlannedTownCenter
Context triple: [Ave Maria, Florida, hasPlannedTownCenter, yes]
  • A. hasPlannedCity
    Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
  • B. hasPlannedCommunity chosen
    Indicates that an entity is associated with or contains a community that has been intentionally designed and organized according to a specific development plan.
  • C. townPlannedWith
    Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
  • D. isPlannedCity
    Indicates that a city has been deliberately designed and constructed according to a pre-established urban plan rather than developing organically over time.
  • E. isPlannedTownComponentOf
    Indicates that a planned town element (such as a district, facility, or infrastructure unit) is designed to be part of a larger planned town or urban development.
  • 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_69ca829851908190b4e03829353ee7c3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3bf56f688190902b95afe42635ec completed March 31, 2026, 3:13 a.m.
PD Predicate disambiguation batch_69cb047a8e4c81909b79e0f0bf56440c completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:14 p.m.