Triple

T2417171
Position Surface form Disambiguated ID Type / Status
Subject Battle of Seonghwan E52331 entity
Predicate JapaneseForceStrength P37795 FINISHED
Object approximately 4,000 soldiers 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: approximately 4,000 soldiers | Statement: [Battle of Seonghwan, JapaneseForceStrength, approximately 4,000 soldiers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: JapaneseForceStrength
Context triple: [Battle of Seonghwan, JapaneseForceStrength, approximately 4,000 soldiers]
  • A. commandingForce2Strength
    Indicates that a commanding force possesses or exerts a particular level or measure of strength.
  • B. objectiveOfJapaneseForces
    Indicates that a specified target, goal, or aim is the military objective pursued by Japanese forces.
  • C. commandingForce1Strength
    Indicates that one entity has a certain level or measure of strength in its role as the primary commanding force over another entity or situation.
  • D. besiegingForce
    Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
  • E. JapaneseAirCommander
    Indicates that one entity serves as a Japanese air force commander in relation to another entity or context.
  • F. None of above. chosen

Provenance (4 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_69ab495622948190bc6bc6e4cddaf645 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abc94eafd481909eeff689e5bf5960 completed March 7, 2026, 6:44 a.m.
PD Predicate disambiguation batch_69abc5a6cbd0819086c0716e266b7ebb completed March 7, 2026, 6:28 a.m.
PDg Predicate description generation batch_69abc6011e348190b6f9c038c7559289 completed March 7, 2026, 6:30 a.m.
Created at: March 6, 2026, 9:42 p.m.