Triple

T2266123
Position Surface form Disambiguated ID Type / Status
Subject Battle of Lundy’s Lane E50148 entity
Predicate BritishForcesType P37555 FINISHED
Object British regular 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: British regular infantry | Statement: [Battle of Lundy’s Lane, BritishForcesType, British regular infantry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: BritishForcesType
Context triple: [Battle of Lundy’s Lane, BritishForcesType, British regular infantry]
  • A. alliedForcesComposition
    Indicates the makeup and relative proportions of different military or paramilitary groups that are joined together as allied forces in a given context.
  • B. FalklandsWarBelligerent
    Indicates that an entity was a participating belligerent (a warring party) in the Falklands War.
  • C. USForces
    Indicates the presence, involvement, or deployment of United States military forces in relation to a specified location, event, or entity.
  • D. fleetStrengthEnglish
    Indicates the relative military or naval power level associated with a fleet, expressed or categorized in English terms.
  • E. mainAlliedPower
    Indicates that an entity serves as a primary or leading ally to another entity within an alliance or coalition.
  • 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_69a88b01e0048190ba96431b5f990ba9 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abc2ea65288190bc8644a07a11dfa9 completed March 7, 2026, 6:17 a.m.
PD Predicate disambiguation batch_69abbdb592588190ac1ef5e8c54575b1 completed March 7, 2026, 5:55 a.m.
PDg Predicate description generation batch_69abc2e97eb0819084acb26cfa4e3946 completed March 7, 2026, 6:17 a.m.
Created at: March 4, 2026, 7:48 p.m.