Triple
T11408067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle Pass (Prospect Park) |
E270290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Revolutionary War memorial site |
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 memorial site Context triple: [Battle Pass (Prospect Park), instanceOf, Revolutionary War memorial site]
-
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.
Civil War site
A Civil War site is a historically significant location where events related to the American Civil War occurred, such as battles, encampments, or military operations, and is preserved or recognized for its cultural and educational value.
-
D.
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.
-
E.
American Civil War era site
An American Civil War era site is a historically significant location—such as a battlefield, fort, encampment, prison, or related structure—directly associated with military, political, or social events of the United States Civil War (1861–1865).
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:34 p.m.