Triple

T14652244
Position Surface form Disambiguated ID Type / Status
Subject Battle of Liegnitz E344016 entity
Predicate hasPrimaryOpponents P13136 FINISHED
Object Mongol cavalry vs European heavy 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: Mongol cavalry vs European heavy cavalry | Statement: [Battle of Liegnitz, hasPrimaryOpponents, Mongol cavalry vs European heavy cavalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimaryOpponents
Context triple: [Battle of Liegnitz, hasPrimaryOpponents, Mongol cavalry vs European heavy cavalry]
  • A. keyOpponents chosen
    Indicates that the subject has primary or most significant opponents identified by the object.
  • B. hasOpposingTeamsLedBy
    Indicates a relationship where a competitive event or context features two opposing teams, each directed or managed by a specific leader.
  • C. hasOpposingSide
    Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
  • D. consideredOpponentsAs
    Indicates that one entity regarded or treated another entity as an opponent or adversary.
  • E. intendedOpponents
    Indicates that one entity is the target or adversary that another entity is meant or designed to oppose or confront.
  • 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_69d822e1a2cc81908e5bb93cf61ce3cc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb517e7648190b9fc73d6cdbb68de completed April 14, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69de6576f0208190aa94d995e797ac38 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:27 a.m.