Triple

T26946739
Position Surface form Disambiguated ID Type / Status
Subject Chichimeca War E678663 entity
Predicate combatantStrategy P4211 FINISHED
Object indigenous hit-and-run attacks 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: indigenous hit-and-run attacks | Statement: [Chichimeca War, combatantStrategy, indigenous hit-and-run attacks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: combatantStrategy
Context triple: [Chichimeca War, combatantStrategy, indigenous hit-and-run attacks]
  • A. combatantStrength
    Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
  • B. fleetStrategy
    Indicates the overarching plan or approach governing how a group of vehicles or vessels is organized, deployed, and operated to achieve specific objectives.
  • C. militaryStrategy chosen
    Indicates a relationship where an entity plans, directs, or is associated with the organized use of armed forces and tactics to achieve military or defense objectives.
  • D. combatant2Commander
    Indicates that a combatant serves under the authority or command of a specific commander.
  • E. strategicCommand
    Indicates that one entity issues high-level, overarching directives or plans that guide the actions or decisions of another 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_69eeeb4d69588190a7c912164a1c37b3 completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69f6247480cc8190a887eedaeb94615c completed May 2, 2026, 4:21 p.m.
PD Predicate disambiguation batch_69f623a7539c8190b71797f583da9f63 completed May 2, 2026, 4:17 p.m.
Created at: April 27, 2026, 6:22 a.m.