Triple

T6474290
Position Surface form Disambiguated ID Type / Status
Subject Battle of El Caney E146030 entity
Predicate usForceComposition P57250 FINISHED
Object Regular U.S. infantry regiments 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: Regular U.S. infantry regiments | Statement: [Battle of El Caney, usForceComposition, Regular U.S. infantry regiments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usForceComposition
Context triple: [Battle of El Caney, usForceComposition, Regular U.S. infantry regiments]
  • A. redForcesComposition
    Indicates the makeup or structure of the red (opposing) forces in terms of their constituent units, capabilities, or elements.
  • B. USForceType chosen
    Indicates the type or category of U.S. military force involved in a given relationship or action.
  • C. UnionForcesType
    Indicates that one entity is associated with, composed of, or characterized by a specific type or category of union forces.
  • D. componentForces
    Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
  • E. USForces
    Indicates the presence, involvement, or deployment of United States military forces in relation to a specified location, event, or entity.
  • 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_69c008fec7408190af7b146dc63d9750 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a32c0188190bcb3c35fc1d796a6 completed March 22, 2026, 10:16 p.m.
PD Predicate disambiguation batch_69c0673f6d48819080e10c85155c7195 completed March 22, 2026, 10:03 p.m.
Created at: March 22, 2026, 4:50 p.m.