Triple

T7705084
Position Surface form Disambiguated ID Type / Status
Subject siege of Orléans (1562) E174591 entity
Predicate aimOfRoyalForces P21103 FINISHED
Object capture the Huguenot stronghold of Orléans 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: capture the Huguenot stronghold of Orléans | Statement: [siege of Orléans (1562), aimOfRoyalForces, capture the Huguenot stronghold of Orléans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimOfRoyalForces
Context triple: [siege of Orléans (1562), aimOfRoyalForces, capture the Huguenot stronghold of Orléans]
  • A. royalistObjective chosen
    Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
  • B. aimOfRome
    Indicates that something is the goal, purpose, or intended objective of Rome.
  • C. aimOfAllies
    Indicates that one entity represents the shared goal or objective pursued collectively by a group of allied entities.
  • D. objectiveOfBritishForces
    Indicates that the referenced entity represents a goal, target, or mission that the British forces aim to achieve or act upon.
  • E. aimOfDanishForces
    Indicates that a specified objective or goal is the intended aim or mission of the Danish military forces.
  • 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_69c6995b3e8c8190833108f883d5f53c completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c70402169481909b219dc5f4a64b9b completed March 27, 2026, 10:26 p.m.
PD Predicate disambiguation batch_69c70165e78c8190bf6b3c34e243cb81 completed March 27, 2026, 10:15 p.m.
Created at: March 27, 2026, 4:03 p.m.