Triple
T37951452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | عكّا العتيقة |
E946754
|
entity |
| Predicate | wasSiegeSiteBy |
P103407
|
FINISHED |
| Object | نابليون بونابرت |
—
|
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: نابليون بونابرت | Statement: [عكّا العتيقة, wasSiegeSiteBy, نابليون بونابرت]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSiegeSiteBy Context triple: [عكّا العتيقة, wasSiegeSiteBy, نابليون بونابرت]
-
A.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related entity.
-
B.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
C.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
D.
siegeRelated
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
E.
wasBesiegedBy
chosen
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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.