Triple

T11640803
Position Surface form Disambiguated ID Type / Status
Subject Battle of Los Angeles (1846) E276653 entity
Predicate sideUSObjective P98518 FINISHED
Object maintain control of Los Angeles 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: maintain control of Los Angeles | Statement: [Battle of Los Angeles (1846), sideUSObjective, maintain control of Los Angeles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sideUSObjective
Context triple: [Battle of Los Angeles (1846), sideUSObjective, maintain control of Los Angeles]
  • A. objectiveOfUSForces chosen
    Indicates that a specified goal, target, or mission serves as an objective assigned to or pursued by U.S. military forces.
  • B. usesObjective
    Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
  • C. UnionObjective
    Indicates that an entity has the goal, purpose, or objective of forming, maintaining, or advancing a union or unified organization.
  • D. objectiveOfUnitedStates
    Indicates that something is an official objective or goal pursued by the United States.
  • E. opponentObjective
    Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a260ab488190ab1c00d9850f3096 completed April 10, 2026, 7:10 a.m.
PD Predicate disambiguation batch_69d85dd94bdc819091fa2ed33eb31624 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.