Triple

T389608
Position Surface form Disambiguated ID Type / Status
Subject Abbasid Caliphate E8851 entity
Predicate militaryFeature P7256 FINISHED
Object use of Turkish slave soldiers (ghilman) 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: use of Turkish slave soldiers (ghilman) | Statement: [Abbasid Caliphate, militaryFeature, use of Turkish slave soldiers (ghilman)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryFeature
Context triple: [Abbasid Caliphate, militaryFeature, use of Turkish slave soldiers (ghilman)]
  • A. militaryCharacteristic chosen
    Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
  • B. militaryFunction
    Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
  • C. warfareCapability
    Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
  • D. militaryMeasure
    Indicates a relationship where an entity undertakes, imposes, or is subject to a specific military-related action, policy, or operational measure.
  • E. groundForces
    Indicates that one entity deploys, commands, or involves military forces operating on land in relation 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_69a2e7f55c60819097aff65ea2ca2832 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec5bdc848190826701590070497b completed Feb. 28, 2026, 1:23 p.m.
PD Predicate disambiguation batch_69a2e96960608190bdd342da9c5ddb5e completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.