Triple
T32968768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | conquest of Crete |
E843449
|
entity |
| Predicate | longestSiege |
P53953
|
FINISHED |
| Object | Siege of Candia |
—
|
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: Siege of Candia | Statement: [conquest of Crete, longestSiege, Siege of Candia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longestSiege Context triple: [conquest of Crete, longestSiege, Siege of Candia]
-
A.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
B.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
C.
siegeDuration
chosen
Indicates the length of time that a siege persists from its beginning to its end.
-
D.
hasMajorSiege
Indicates that a significant or large-scale siege event occurred involving the related entities.
-
E.
sieged
Indicates that one entity has surrounded and blockaded another entity or location, typically to cut off supplies and force surrender.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1a5e6a881908df6ec45496a8d1d |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.