Triple
T30884321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Shaykan |
E786716
|
entity |
| Predicate | EgyptianForceComposition |
P6154
|
FINISHED |
| Object | Egyptian regulars |
—
|
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: Egyptian regulars | Statement: [Battle of Shaykan, EgyptianForceComposition, Egyptian regulars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EgyptianForceComposition Context triple: [Battle of Shaykan, EgyptianForceComposition, Egyptian regulars]
-
A.
combatantStrengthEgyptian
Indicates that the entity has combatant strength or military capability associated with Egyptian forces or context.
-
B.
USForceStrength
Indicates the level or magnitude of military forces deployed or available by the United States in a given context.
-
C.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
D.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
E.
GermanForceStrength
Indicates the size or level of military power possessed by German forces in a given context.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69204be748190a6a2a401d81c1218 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:48 p.m.