Triple
T4138824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Las Navas de Tolosa |
E89222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Reconquista |
C13076
|
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: event in the Reconquista Context triple: [Battle of Las Navas de Tolosa, instanceOf, event in the Reconquista]
-
A.
event in the history of Spain
An event in the history of Spain is a significant occurrence or development within Spanish territory or involving Spanish actors that has contributed to shaping the nation’s political, social, cultural, or economic trajectory over time.
-
B.
event in the Eighty Years' War
An event in the Eighty Years' War is a specific historical occurrence—such as a battle, treaty, siege, or political decision—that took place between 1568 and 1648 and significantly influenced the course or outcome of the Dutch struggle for independence from Spanish rule.
-
C.
medieval event
A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
-
D.
faction in the Spanish Civil War
A faction in the Spanish Civil War is a politically or ideologically aligned group—such as Republicans, Nationalists, anarchists, or regional nationalists—that organized military and political efforts in pursuit of its vision for Spain during the 1936–1939 conflict.
-
E.
13th-century event
chosen
A 13th-century event is any significant occurrence, development, or happening that took place between the years 1201 and 1300 CE.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:43 p.m.