Triple
T3763295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Horseshoe (alleged) |
E82612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | controversial historical claim |
C3523
|
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: controversial historical claim Context triple: [Operation Horseshoe (alleged), instanceOf, controversial historical claim]
-
A.
contentious case
A contentious case is a legal dispute between opposing parties brought before a court or tribunal for adjudication on contested rights or obligations.
-
B.
historical myth
A historical myth is a widely held narrative about past events that blends factual history with legend, symbolism, or cultural interpretation, often shaping collective identity more than accurately recording what occurred.
-
C.
revisionist historical narrative
chosen
A revisionist historical narrative is an account of past events that challenges established interpretations by reexamining evidence, perspectives, and assumptions to present an alternative understanding of history.
-
D.
historical topic
A historical topic is a specific subject, event, period, or theme from the past that is studied, analyzed, and interpreted to understand historical developments and their impact.
-
E.
scientific controversy
A scientific controversy is a sustained public or professional disagreement among scientists over the interpretation of evidence, validity of methods, or implications of findings within a particular field of research.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.