Triple
T30884327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Shaykan |
E786716
|
entity |
| Predicate | casualtiesEgyptianSide |
P171603
|
FINISHED |
| Object | several thousand killed |
—
|
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: several thousand killed | Statement: [Battle of Shaykan, casualtiesEgyptianSide, several thousand killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesEgyptianSide Context triple: [Battle of Shaykan, casualtiesEgyptianSide, several thousand killed]
-
A.
casualtiesAtTobruk
Indicates that an entity experienced casualties (killed, wounded, or missing) in connection with the events at Tobruk.
-
B.
militaryCasualtiesSide
Indicates the side or party in a conflict to which the recorded military casualties belong.
-
C.
combatantStrengthEgyptian
Indicates that the entity has combatant strength or military capability associated with Egyptian forces or context.
-
D.
casualtiesKharijites
Indicates that there were casualties suffered by the Kharijites in a given event or context.
-
E.
casualtiesJordan
Indicates that an event or action resulted in casualties (deaths or injuries) among people in Jordan.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 8:48 p.m.