Triple

T5699821
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kilsyth (1645) E125630 entity
Predicate CovenanterForcesIncluded P65659 FINISHED
Object Lowland infantry 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: Lowland infantry | Statement: [Battle of Kilsyth (1645), CovenanterForcesIncluded, Lowland infantry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: CovenanterForcesIncluded
Context triple: [Battle of Kilsyth (1645), CovenanterForcesIncluded, Lowland infantry]
  • A. royalistForcesIncluded
    Indicates that the composition of the royalist forces included the specified entity or group.
  • B. numberOfSiegesDuringEnglishCivilWar
    Indicates the count of distinct siege events that occurred during the English Civil War involving the given entity.
  • C. engagedForces
    Indicates that one force has actively committed or deployed its military units against another force in combat or operational interaction.
  • D. RoyalistForceStrength
    Indicates the size or level of military power possessed by a royalist-aligned force in a given context.
  • E. ScottishCasualties
    Indicates that an event or situation resulted in casualties (deaths or injuries) among Scottish individuals or forces.
  • 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_69c0082c96988190b3a6a201edce472a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0241030408190be774a5d2ca6e999 completed March 22, 2026, 5:17 p.m.
PD Predicate disambiguation batch_69c021c2d8bc8190b947c7d1f423d2f3 completed March 22, 2026, 5:07 p.m.
PDg Predicate description generation batch_69c023dfec6881909ee6189b874b4348 completed March 22, 2026, 5:16 p.m.
Created at: March 22, 2026, 3:45 p.m.