Triple

T24545673
Position Surface form Disambiguated ID Type / Status
Subject California annexation by the United States E607216 entity
Predicate militaryCommanderInvolved P42241 FINISHED
Object Stephen W. Kearny NE NERFINISHED

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: Stephen W. Kearny | Statement: [California annexation by the United States, militaryCommanderInvolved, Stephen W. Kearny]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryCommanderInvolved
Context triple: [California annexation by the United States, militaryCommanderInvolved, Stephen W. Kearny]
  • A. commandersInvolved chosen
    Indicates that specific commanders participated in, oversaw, or were directly involved in a particular event, operation, or engagement.
  • B. engagedWithCommander
    Indicates that an entity is actively interacting, communicating, or collaborating with a commander in an operational or authoritative context.
  • C. isMilitaryCommand
    Indicates that one entity holds formal military authority or command over another entity or group.
  • D. militaryConflictOversaw
    Indicates that one party had authoritative oversight or command responsibility over a military conflict involving another party.
  • E. combatant2Commander
    Indicates that a combatant serves under the authority or command of a specific commander.
  • 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_69e2c4c9bf94819082d05da6f5c29907 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2be044d4c819094e14eda28d371a7 completed April 30, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f2a6b0ca8081908d931aec560eae56 completed April 30, 2026, 12:47 a.m.
Created at: April 18, 2026, 2:26 a.m.