Triple

T36557691
Position Surface form Disambiguated ID Type / Status
Subject Iron Hills E901738 entity
Predicate providesTroopsFor P15397 FINISHED
Object Battle of Five Armies 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: Battle of Five Armies | Statement: [Iron Hills, providesTroopsFor, Battle of Five Armies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: providesTroopsFor
Context triple: [Iron Hills, providesTroopsFor, Battle of Five Armies]
  • A. suppliedTroopsTo chosen
    Indicates that one entity provided military personnel or forces to another entity.
  • B. typeOfTroops
    Indicates the specific category or kind of military forces involved in or associated with an entity or event.
  • C. commandedTroopsAt
    Indicates that a person held command authority over military forces at a specific location or during a particular operation.
  • D. commandedForcesOf
    Indicates that one entity held command authority over the military or armed forces associated with another entity.
  • E. garrisonedForce
    Indicates that a military force is stationed in and occupies a specific location, typically for defense or control.
  • 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_69f76e634e9481908c9ba1b87ab87c26 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69feb342994081909481ec8ec5d44928 completed May 9, 2026, 4:08 a.m.
PD Predicate disambiguation batch_69feb046e4e48190b96649aa28529cc9 completed May 9, 2026, 3:55 a.m.
Created at: May 3, 2026, 4:11 p.m.