Triple

T24951741
Position Surface form Disambiguated ID Type / Status
Subject First Army (North German Confederation) E624356 entity
Predicate engagementResultAtBattleOfGravelotte P157876 FINISHED
Object German tactical success 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: German tactical success | Statement: [First Army (North German Confederation), engagementResultAtBattleOfGravelotte, German tactical success]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: engagementResultAtBattleOfGravelotte
Context triple: [First Army (North German Confederation), engagementResultAtBattleOfGravelotte, German tactical success]
  • A. allyDuringAustroPrussianWar
    Indicates that one entity was an ally of another during the Austro-Prussian War.
  • B. resultInArdennes
    Indicates that one event, action, or condition leads to or causes an outcome specifically occurring in the Ardennes region.
  • C. resultOfTannenbergForGermany
    Indicates the outcome or consequence that the Battle of Tannenberg had specifically for Germany.
  • D. enemyEngagementAtJutland
    Indicates that an entity participated in or was involved in hostile military action against an enemy during the Battle of Jutland.
  • E. placeOfMainEngagement
    Indicates the primary location where an entity carries out its main activities, operations, or engagements.
  • 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_69e2ff22e4c48190a0444b5a044f14e8 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f453035f508190be83a3d521723acf completed May 1, 2026, 7:15 a.m.
PD Predicate disambiguation batch_69f44d77f6e88190a4643ab2cbef567b completed May 1, 2026, 6:51 a.m.
PDg Predicate description generation batch_69f45300bd488190bb1d4160f5534ef6 completed May 1, 2026, 7:15 a.m.
Created at: April 18, 2026, 5:57 a.m.