Triple
T31053557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Cádiz |
E791333
|
entity |
| Predicate | hasCapitalCityUnderSiege |
P92602
|
FINISHED |
| Object | Cádiz |
—
|
NE NERFINISHED |
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: Cádiz | Statement: [Siege of Cádiz, hasCapitalCityUnderSiege, Cádiz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalCityUnderSiege Context triple: [Siege of Cádiz, hasCapitalCityUnderSiege, Cádiz]
-
A.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
B.
cityStatusDuringSiege
Indicates the condition or status of a city specifically during the period in which it is under siege.
-
C.
siegeOccurredIn
chosen
Indicates that a siege took place within or at the location specified by the related entity.
-
D.
hasBesiegingSide
Indicates that one party is the attacking or besieging side in a siege or military encirclement of another.
-
E.
citySacked
Indicates that a city has been violently attacked, looted, and destroyed or heavily damaged, typically as a result of military conquest.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 29, 2026, 9 p.m.