Triple

T5893154
Position Surface form Disambiguated ID Type / Status
Subject Ottoman army caught while crossing the Tisa River E131037 entity
Predicate hasResultForOttomans P64506 FINISHED
Object loss of experienced troops 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: loss of experienced troops | Statement: [Ottoman army caught while crossing the Tisa River, hasResultForOttomans, loss of experienced troops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasResultForOttomans
Context triple: [Ottoman army caught while crossing the Tisa River, hasResultForOttomans, loss of experienced troops]
  • A. outcomeForOttomans chosen
    Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
  • B. OttomanRole
    Indicates that an entity holds or held a specific role, position, or function within the Ottoman Empire.
  • C. OttomanCommander
    Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
  • D. wasOttomanCity
    Indicates that a location previously functioned as a city within the territorial or administrative domain of the Ottoman Empire.
  • E. primaryTacticOttomans
    Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
  • 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_69c00857439c819095950754176aa58a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0400f1af881908d376ea4793f6dea completed March 22, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69c0334dc8248190b7394dcece362d52 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 3:58 p.m.