Triple

T7202547
Position Surface form Disambiguated ID Type / Status
Subject Abu Sufyan ibn Harb E148581 entity
Predicate sideInBattleOfHunayn P75790 FINISHED
Object Muslims 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 | Statement: [Abu Sufyan ibn Harb, sideInBattleOfHunayn, Muslims]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sideInBattleOfHunayn
Context triple: [Abu Sufyan ibn Harb, sideInBattleOfHunayn, Muslims]
  • A. sideInBattleOfBadr
    Indicates the role or allegiance an entity had on a particular side during the Battle of Badr.
  • B. garrisonSide
    Indicates the side, faction, or allegiance that a garrison is associated with or belongs to.
  • C. MamlukCommander
    Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
  • D. opponentAtBattleOfTheNile
    Indicates that one entity was an opposing combatant of the other in the Battle of the Nile.
  • E. primaryByzantineForces
    Indicates that the referenced forces constitute the main or principal military contingent of the Byzantine side in a given context or engagement.
  • F. None of above. chosen

Provenance (4 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_69c687e8cf188190b5f3ecffd681f04e completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e94a9ee4819086de79fcdfa1836a completed March 27, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69c6e757fed4819091b0a096e3befc3a completed March 27, 2026, 8:23 p.m.
PDg Predicate description generation batch_69c6e8fd9b848190b2b1beea5698422b completed March 27, 2026, 8:30 p.m.
Created at: March 27, 2026, 2:52 p.m.