Triple

T5285742
Position Surface form Disambiguated ID Type / Status
Subject French Aerostatic Corps E119613 entity
Predicate roleAtBattleOfFleurus P28183 FINISHED
Object observed enemy troop movements 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: observed enemy troop movements | Statement: [French Aerostatic Corps, roleAtBattleOfFleurus, observed enemy troop movements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfFleurus
Context triple: [French Aerostatic Corps, roleAtBattleOfFleurus, observed enemy troop movements]
  • A. notableBattleRole chosen
    Indicates the specific role or function an entity played in a notable or historically significant battle.
  • B. laterFoughtAlongside
    Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
  • C. foughtUnderRuler
    Indicates that one entity engaged in combat or military service under the authority, command, or leadership of another entity (the ruler).
  • D. notableCommanderSide
    Indicates that a particular military or strategic side is notably commanded or led by a specified commander.
  • E. roleInFronde
    Indicates that an entity participated in or held a specific role within the historical conflict known as the Fronde.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd8c9c72b08190947b6b955ac1bb5a completed March 20, 2026, 6:06 p.m.
PD Predicate disambiguation batch_69bd844a56b48190ad743c42246e02dd completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:52 p.m.