Triple
T24978634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glover’s Rock |
E625099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Revolutionary War monument |
C3992
|
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: Revolutionary War monument Context triple: [Glover’s Rock, instanceOf, Revolutionary War monument]
-
A.
Revolutionary War site
A Revolutionary War site is a historically significant location where events, battles, encampments, or strategic activities related to the American Revolutionary War took place and are preserved or interpreted today.
-
B.
American Revolutionary War site
chosen
An American Revolutionary War site is a historically significant location where events related to the American struggle for independence—such as battles, encampments, political actions, or key decisions—took place and are preserved or commemorated today.
-
C.
American Civil War monument
An American Civil War monument is a commemorative structure or sculpture erected to honor individuals, units, or events associated with the United States Civil War, often serving as a site of historical memory and public reflection.
-
D.
memorial to George Washington
A memorial to George Washington is a commemorative structure or site dedicated to honoring and preserving the legacy, leadership, and historical significance of the first President of the United States.
-
E.
colonial-era monument
A colonial-era monument is a public structure or statue erected during or commemorating a period of colonial rule, symbolizing the power, values, and historical narratives of the colonizing authority.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:02 a.m.