Triple
T6691982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikrima ibn Abi Jahl |
E152648
|
entity |
| Predicate | sideInBattleOfUhud |
P375
|
FINISHED |
| Object | Quraysh polytheists |
—
|
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: Quraysh polytheists | Statement: [Ikrima ibn Abi Jahl, sideInBattleOfUhud, Quraysh polytheists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInBattleOfUhud Context triple: [Ikrima ibn Abi Jahl, sideInBattleOfUhud, Quraysh polytheists]
-
A.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
B.
garrisonSide
Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
-
C.
laterFoughtAlongside
Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
-
D.
roleInArabRevolt
Indicates that an entity played a specific role or had a particular involvement in the Arab Revolt.
-
E.
belligerentSideOfVictims
Indicates that the referenced party is the side or faction to which the victims in a conflict or hostile situation belong.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:05 p.m.