Triple
T9152814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennebunkport Historical Society properties |
E219629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collection of historic properties |
C4549
|
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: collection of historic properties Context triple: [Kennebunkport Historical Society properties, instanceOf, collection of historic properties]
-
A.
group of historic sites
chosen
A group of historic sites is a collection of geographically or thematically related locations that hold recognized cultural, architectural, or historical significance and are often managed or interpreted as a unified whole.
-
B.
serial heritage property
A serial heritage property is a collection of two or more geographically separate but related heritage components that together express a single, coherent cultural or natural significance.
-
C.
Historic house
A historic house is a residential building recognized for its significant architectural, cultural, or historical value, often preserved or restored to reflect the period in which it was built.
-
D.
residential historic district
A residential historic district is a geographically defined neighborhood composed primarily of homes that collectively reflect significant historical, architectural, or cultural characteristics from a particular period or periods.
-
E.
historical district
A historical district is a geographically defined area recognized for its concentration of buildings, structures, and sites that collectively reflect significant cultural, architectural, or historical heritage.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:20 p.m.