Triple
T30196504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kufra |
E767644
|
entity |
| Predicate | besiegedPlace |
P113825
|
FINISHED |
| Object | El Tag fort |
—
|
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: El Tag fort | Statement: [Battle of Kufra, besiegedPlace, El Tag fort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: besiegedPlace Context triple: [Battle of Kufra, besiegedPlace, El Tag fort]
-
A.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
-
B.
fortificationTypeBesieged
chosen
Indicates that a specific type of fortification is the target of a siege or besieging action.
-
C.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
D.
fortifiedSite
Indicates a site that has been strengthened or defended with protective structures or measures against attack.
-
E.
wasBesiegedBy
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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f879cd88190989f5c86990caf3f |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:29 p.m.