Triple

T24812513
Position Surface form Disambiguated ID Type / Status
Subject siege of Diriyah E620825 entity
Predicate combatantStrengthOttomanSide P131194 FINISHED
Object several thousand troops 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: several thousand troops | Statement: [siege of Diriyah, combatantStrengthOttomanSide, several thousand troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantStrengthOttomanSide
Context triple: [siege of Diriyah, combatantStrengthOttomanSide, several thousand troops]
  • A. OttomanStrength chosen
    Indicates the level or degree of military, political, or economic power possessed or exerted by the Ottoman Empire in a given context.
  • B. OttomanForcesIncluded
    Indicates that the composition of a military force or contingent included units or personnel from the Ottoman forces.
  • C. OttomanCommander
    Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
  • D. combatantStrengthAustrianSide
    Indicates that the associated entity represents the strength or size of the Austrian side’s combatant forces in a conflict.
  • E. primaryAdversaryOfOttomans
    Indicates that one entity served as the main or most significant opponent or rival to the Ottoman Empire.
  • 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_69e2fabfd4648190bd0e5c7f4dbb6cab completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 4:51 a.m.