Triple
T9108838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | demonstrated defensive strength of Castillo de San Marcos |
E218543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military outcome |
C16784
|
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: historical military outcome Context triple: [demonstrated defensive strength of Castillo de San Marcos, instanceOf, historical military outcome]
-
A.
military operation outcome
chosen
A military operation outcome is the overall result or consequence of a planned military action, encompassing its achieved objectives, strategic impact, and associated costs or losses.
-
B.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
-
C.
year of military victories
A year of military victories represents a specific calendar year characterized by a notable concentration of successful military engagements or campaigns achieved by a particular state, alliance, or armed force.
-
D.
historic battlefield
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
-
E.
historical armed forces
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:16 p.m.