Triple

T10074734
Position Surface form Disambiguated ID Type / Status
Subject Georgetown, Texas E213720 entity
Predicate hasPolicyReputation P85020 FINISHED
Object support for historic preservation 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: support for historic preservation | Statement: [Georgetown, Texas, hasPolicyReputation, support for historic preservation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPolicyReputation
Context triple: [Georgetown, Texas, hasPolicyReputation, support for historic preservation]
  • A. hasPolicyReputationFor chosen
    Indicates that an entity is recognized or regarded in a particular way with respect to its policies or policy-related behavior.
  • B. hasPolicyStatus
    Indicates that an entity is associated with a policy and specifies the current status or state of that policy.
  • C. securityReputation
    Indicates the assessed trustworthiness or risk level associated with an entity’s security posture or behavior.
  • D. hasQuirkyReputation
    Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
  • E. scoringReputation
    Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
  • 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_69ca839add308190b57d53b4ec21f2d0 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdd017b8288190a577bd66e4ba66b7 completed April 2, 2026, 2:10 a.m.
PD Predicate disambiguation batch_69cd4b97870481908f7a89df10d58a9e completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 8:59 p.m.