Triple
T27356814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamestown Rediscovery project |
E685706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic preservation initiative |
C5247
|
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 preservation initiative Context triple: [Jamestown Rediscovery project, instanceOf, historic preservation initiative]
-
A.
historic preservation project
chosen
A historic preservation project is a coordinated effort to identify, protect, restore, and maintain buildings, sites, or artifacts of historical, cultural, or architectural significance for present and future generations.
-
B.
historic preservation subject
A historic preservation subject is any building, site, structure, object, or district recognized for its historical, architectural, cultural, or archaeological significance and considered for protection, conservation, or restoration.
-
C.
historic preservation fund
A historic preservation fund is a financial resource or program dedicated to supporting the protection, restoration, and maintenance of historically significant buildings, sites, and artifacts.
-
D.
historic preservation commission
A historic preservation commission is a governing body that identifies, protects, and regulates historically significant buildings, sites, and districts within a community.
-
E.
historic preservation organization
A historic preservation organization is a group dedicated to identifying, protecting, and promoting buildings, sites, and artifacts of historical, cultural, or architectural significance.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 11:51 a.m.