Triple
T26147152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvale Church Row Historic District |
E659703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic site in Georgia |
C11600
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historic site in Georgia Context triple: [Louvale Church Row Historic District, instanceOf, historic site in Georgia]
-
A.
protected area of Georgia
A protected area of Georgia is a designated geographic region within the state set aside and managed to conserve its natural, cultural, or recreational resources under specific legal and administrative safeguards.
-
B.
Historic site
chosen
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
C.
historic place in Massachusetts
A historic place in Massachusetts is a location, structure, or district within the state that holds recognized significance for its association with important events, people, architecture, or cultural heritage, often preserved and documented for its contribution to local or national history.
-
D.
New York State Historic Site
A New York State Historic Site is a location officially designated and managed by New York State for its significant historical, cultural, or architectural importance.
-
E.
historic district in Florida
A historic district in Florida is a geographically defined area recognized for its concentration of buildings, structures, and sites that reflect the architectural, cultural, and historical heritage of the state, often protected through local, state, or national preservation programs.
- F. None of above.
Provenance (1 batch)
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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
Created at: April 26, 2026, 8:23 p.m.