Triple
T28750425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Campaign of the American Revolution Parks Group |
E731508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collection of historic sites |
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 sites Context triple: [Southern Campaign of the American Revolution Parks Group, instanceOf, collection of historic sites]
-
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.
Historic site
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
C.
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.
-
D.
reconstructed historic site
A reconstructed historic site is a place where buildings, structures, or environments from the past have been rebuilt or significantly restored to approximate their original appearance and context for educational, commemorative, or touristic purposes.
-
E.
historic park
A historic park is a preserved outdoor area that combines natural landscapes with sites, structures, and artifacts of historical significance for public education and recreation.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:07 a.m.