Triple
T35731522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman sieges of Corfu |
E1032762
|
entity |
| Predicate | controlledByDuringSieges |
P198612
|
FINISHED |
| Object | Republic of Venice |
—
|
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: Republic of Venice | Statement: [Ottoman sieges of Corfu, controlledByDuringSieges, Republic of Venice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByDuringSieges Context triple: [Ottoman sieges of Corfu, controlledByDuringSieges, Republic of Venice]
-
A.
controlledByBeforeSiege
Indicates that an entity exercised control over another entity or location prior to the onset of a siege.
-
B.
cityStatusDuringSiege
Indicates the condition or status of a city specifically during the period in which it is under siege.
-
C.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
D.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
E.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
| PDg | Predicate description generation | batch_69fef5cec8208190b85665ab6a511a08 |
completed | May 9, 2026, 8:52 a.m. |
Created at: May 3, 2026, 4:05 p.m.