Triple

T10887793
Position Surface form Disambiguated ID Type / Status
Subject Lunga Ridge E257093 entity
Predicate resultOfKeyBattle P1703 FINISHED
Object Allied defensive victory 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: Allied defensive victory | Statement: [Lunga Ridge, resultOfKeyBattle, Allied defensive victory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resultOfKeyBattle
Context triple: [Lunga Ridge, resultOfKeyBattle, Allied defensive victory]
  • A. resultOfBattle
    Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
  • B. hasKeyBattle chosen
    Indicates that an entity is associated with a major or decisive battle that is central to its history, role, or significance.
  • C. battleOutcomeRole
    Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
  • D. keyBattlegroundState
    Indicates that a location is considered a crucial battleground state whose outcome is highly influential in determining the overall result of an election.
  • E. mainBattle
    Indicates that one battle is the primary or most significant engagement associated with a particular conflict, campaign, 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_69d6aa848804819081b2713ca0bedf06 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d75201e6888190a2bc41a17784eec3 completed April 9, 2026, 7:15 a.m.
PD Predicate disambiguation batch_69d70d3943c881908895397eccc3e415 completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:21 p.m.