Triple
T31122817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Cádiz (1823) |
E793267
|
entity |
| Predicate | controlledByBeforeSiege |
P194812
|
FINISHED |
| Object | liberal Spanish government |
—
|
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: liberal Spanish government | Statement: [siege of Cádiz (1823), controlledByBeforeSiege, liberal Spanish government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByBeforeSiege Context triple: [siege of Cádiz (1823), controlledByBeforeSiege, liberal Spanish government]
-
A.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
B.
hasBesiegingSide
Indicates that one party is the attacking or besieging side in a siege or military encirclement of another.
-
C.
isEarlierSiegeOf
Indicates that one siege occurred before another siege in time.
-
D.
cityStatusDuringSiege
Indicates the condition or status of a city specifically during the period in which it is under siege.
-
E.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
- F. None of above. chosen
Provenance (4 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: April 29, 2026, 9:05 p.m.