Triple

T2046669
Position Surface form Disambiguated ID Type / Status
Subject Battle of Tweebosch E45467 entity
Predicate commandingForce1Strength P36038 FINISHED
Object approximately 1,500 Boers 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: approximately 1,500 Boers | Statement: [Battle of Tweebosch, commandingForce1Strength, approximately 1,500 Boers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: commandingForce1Strength
Context triple: [Battle of Tweebosch, commandingForce1Strength, approximately 1,500 Boers]
  • A. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • B. commandedForcesOf
    Indicates that one entity held command authority over the military or armed forces associated with another entity.
  • C. besiegingForce
    Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
  • D. typeOfTroops
    Indicates the specific category or kind of military forces involved in or associated with an entity or event.
  • E. garrisonedForce
    Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
  • 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_69a8891948208190ab7898da21824c77 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abbc2c3f6c8190aff07097b2654e52 completed March 7, 2026, 5:48 a.m.
PD Predicate disambiguation batch_69abb7aa00d4819086d347d9a08f81a0 completed March 7, 2026, 5:29 a.m.
PDg Predicate description generation batch_69abbc2b07d48190ba9d67353167b472 completed March 7, 2026, 5:48 a.m.
Created at: March 4, 2026, 7:39 p.m.