Triple

T30506328
Position Surface form Disambiguated ID Type / Status
Subject Battle of Carthage (1861) E776279 entity
Predicate strengthMissouriStateGuard P169800 FINISHED
Object approximately 4,000–6,000 men 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 4,000–6,000 men | Statement: [Battle of Carthage (1861), strengthMissouriStateGuard, approximately 4,000–6,000 men]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: strengthMissouriStateGuard
Context triple: [Battle of Carthage (1861), strengthMissouriStateGuard, approximately 4,000–6,000 men]
  • A. strengthType
    Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
  • B. strengthTiedTo
    Indicates that the degree of strength or power of one entity is directly dependent on or correlated with another specified factor or entity.
  • C. strengthDescription
    Indicates a description or characterization of the degree of strength associated with an entity or relationship.
  • D. strengthFeat
    Indicates that an entity performs or demonstrates a notable feat of physical strength in relation to another entity or object.
  • E. strengthPeak
    Indicates the point or period at which an entity’s strength reaches its maximum level.
  • 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_69f2249a155c8190b1d512106007e9bb completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f687b4dddc8190a59fd13d2f8a2e16 completed May 2, 2026, 11:24 p.m.
PD Predicate disambiguation batch_69f67e42d6688190b60e91d2c388c555 completed May 2, 2026, 10:44 p.m.
PDg Predicate description generation batch_69f6827a7b9c8190ab13605aacc81df9 completed May 2, 2026, 11:02 p.m.
Created at: April 29, 2026, 8:15 p.m.