Triple

T2600366
Position Surface form Disambiguated ID Type / Status
Subject Battle of Bannockburn E58326 entity
Predicate EnglishForcesCharacteristic P662 FINISHED
Object heavily armoured cavalry 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: heavily armoured cavalry | Statement: [Battle of Bannockburn, EnglishForcesCharacteristic, heavily armoured cavalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: EnglishForcesCharacteristic
Context triple: [Battle of Bannockburn, EnglishForcesCharacteristic, heavily armoured cavalry]
  • A. hasCharacteristic
    Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
  • B. languageCharacterizedBy
    Indicates that a language is defined or distinguished by a particular feature, property, or characteristic.
  • C. equipmentCharacteristic
    Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
  • D. linguisticFeature
    Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
  • E. characterizedBy chosen
    Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
  • 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_69ab4ac14040819098b13f4a27d5c8ff completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abd457564c819080d8c8818c02545a completed March 7, 2026, 7:31 a.m.
PD Predicate disambiguation batch_69abd0d4e8648190b612eb09aa085451 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:49 p.m.