Triple

T28398567
Position Surface form Disambiguated ID Type / Status
Subject Battle of the Bridge E719343 entity
Predicate SasanianForcesStrength P164458 FINISHED
Object larger than Rashidun forces 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: larger than Rashidun forces | Statement: [Battle of the Bridge, SasanianForcesStrength, larger than Rashidun forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: SasanianForcesStrength
Context triple: [Battle of the Bridge, SasanianForcesStrength, larger than Rashidun forces]
  • A. sideSasanian
    Indicates that an entity is aligned with, belongs to, or is on the side of the Sasanian faction or polity in a given context.
  • B. SaxonForcesStrength
    Indicates the level or magnitude of military power possessed by Saxon forces in a given context.
  • C. ParthianForceType
    Indicates the type or classification of a military force associated with the Parthians.
  • D. estimatedRomanForces
    Indicates that a specified quantity represents an estimate of the size or strength of Roman military forces involved in a particular context or event.
  • E. PersianForceComponent
    Indicates that an entity functions as a constituent unit or sub-force within a larger Persian military force or formation.
  • 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_69eff6efd1b08190ae3cefd4f11388a2 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64cf1aa7c8190b146b26dd4291025 completed May 2, 2026, 7:13 p.m.
PD Predicate disambiguation batch_69f641e2f1708190b45b48d6a43c51d2 completed May 2, 2026, 6:26 p.m.
PDg Predicate description generation batch_69f64bca8574819095e081cbb7e2f369 completed May 2, 2026, 7:08 p.m.
Created at: April 28, 2026, 1:18 a.m.