Triple
T2225265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manzanar National Historic Site |
E48634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II historic site |
C702
|
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: World War II historic site Context triple: [Manzanar National Historic Site, instanceOf, World War II historic site]
-
A.
World War II site
chosen
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
B.
World War II front
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
C.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
D.
theater of World War II
The theater of World War II is a conceptual class representing a distinct geographic region and operational context in which military campaigns, battles, and strategic activities of the war were planned, conducted, and coordinated.
-
E.
Holocaust site
A Holocaust site is a location directly associated with the persecution, deportation, forced labor, or mass murder of Jews and other targeted groups by Nazi Germany and its collaborators during the Holocaust.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:47 p.m.