Triple
T12904744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Civil War heritage tourism network |
E308702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic sites network |
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: historic sites network Context triple: [United States Civil War heritage tourism network, instanceOf, historic sites network]
-
A.
World Heritage site
A World Heritage site is a landmark or area recognized by UNESCO as having outstanding universal value to humanity for its cultural, natural, or mixed significance, warranting protection and preservation for future generations.
-
B.
national heritage site
A national heritage site is a location, structure, or landscape officially designated by a country as having significant historical, cultural, architectural, or natural value warranting legal protection and preservation.
-
C.
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.
-
D.
cultural site
A cultural site is a place of historical, artistic, social, or spiritual significance that embodies and preserves the traditions, values, and heritage of a community or civilization.
-
E.
archaeological site network
An archaeological site network is a conceptual framework representing interconnected archaeological sites and their relationships through spatial, temporal, cultural, and material linkages.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:40 p.m.