Triple
T9531063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Amana, Iowa |
E229894
|
entity |
| Predicate | isPartOfHistoricDistrict |
P51598
|
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: [High Amana, Iowa, isPartOfHistoricDistrict, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfHistoricDistrict Context triple: [High Amana, Iowa, isPartOfHistoricDistrict, true]
-
A.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
B.
sharesHistoricDistrictWith
Indicates that two entities are located within or associated with the same designated historic district.
-
C.
hasHistoricDistrictAssociation
chosen
Indicates a relationship in which an entity is associated with, linked to, or part of a designated historic district.
-
D.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
E.
hasHistoricPreservationOverlayZone
Indicates that a property or area is designated within a special zoning district established to protect its historic character or features.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b408648190a04127c1d47fe7d2 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.