Triple
T31082639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fada |
E792141
|
entity |
| Predicate | casualtiesLibyanKilled |
P171313
|
FINISHED |
| Object | approximately 784 |
—
|
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: approximately 784 | Statement: [Battle of Fada, casualtiesLibyanKilled, approximately 784]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casualtiesLibyanKilled Context triple: [Battle of Fada, casualtiesLibyanKilled, approximately 784]
-
A.
casualtiesLibya
chosen
Indicates the occurrence or count of people killed or injured in events taking place in Libya.
-
B.
casualtiesKharijites
Indicates that there were casualties suffered by the Kharijites in a given event or context.
-
C.
statusInLibya
Indicates the legal, social, or political condition or standing that an entity holds within the context of Libya.
-
D.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
E.
claimedLimitByLibya
Indicates that a specified limit, boundary, or extent is asserted or claimed by Libya as its own.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 9:02 p.m.