Triple
T8670149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Badr site |
E205773
|
entity |
| Predicate | battleBelligerentSide |
P375
|
FINISHED |
| Object | Muslims of Medina |
—
|
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: Muslims of Medina | Statement: [Battle of Badr site, battleBelligerentSide, Muslims of Medina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleBelligerentSide Context triple: [Battle of Badr site, battleBelligerentSide, Muslims of Medina]
-
A.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
B.
battleBelligerentAtSite
Indicates that a particular belligerent (participant in a battle) was present and engaged in that battle at a specified site or location.
-
C.
countryDuringBattle
Indicates that a specified country was involved in or existed as a relevant participant or context during a particular battle.
-
D.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
E.
combatantsNationality
Indicates that the entities involved in a combat or conflict share or are associated with a specified nationality.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4917cb9881909a73b74e54250613 |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.