Triple
T8670155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Badr site |
E205773
|
entity |
| Predicate | numberOfQurayshFightersApprox |
P6153
|
FINISHED |
| Object | about 1000 |
—
|
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: about 1000 | Statement: [Battle of Badr site, numberOfQurayshFightersApprox, about 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfQurayshFightersApprox Context triple: [Battle of Badr site, numberOfQurayshFightersApprox, about 1000]
-
A.
sideInBattleOfHunayn
Indicates that an entity participated as a side (party or faction) in the Battle of Hunayn.
-
B.
sideInBattleOfBadr
Indicates the role or allegiance an entity had on a particular side during the Battle of Badr.
-
C.
المنصب_في_قريش
Indicates that a person holds or held a specific official or social position within the Quraysh tribe.
-
D.
numberOfTroopsInvolved
chosen
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
-
E.
attackingForceApprox
Indicates that one entity is the approximate attacking force, in terms of size or strength, relative to another entity or 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_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.