Triple
T13908891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of the Alcázar (1936) |
E334431
|
entity |
| Predicate | besiegersIncluded |
P64964
|
FINISHED |
| Object | Republican militia |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Republican militia | Statement: [Siege of the Alcázar (1936), besiegersIncluded, Republican militia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: besiegersIncluded Context triple: [Siege of the Alcázar (1936), besiegersIncluded, Republican militia]
-
A.
besieger
chosen
Indicates that one entity is laying siege to, or conducting a siege against, another entity.
-
B.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
-
C.
besiegingForce
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
D.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
E.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
- F. None of above.
Provenance (3 batches)
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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2721ec6c8190888f4a9d004eb8e0 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.