Triple

T30488687
Position Surface form Disambiguated ID Type / Status
Subject Operation Ripper E775796 entity
Predicate frontLineAdvance P126780 FINISHED
Object advance toward the 38th parallel 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: advance toward the 38th parallel | Statement: [Operation Ripper, frontLineAdvance, advance toward the 38th parallel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: frontLineAdvance
Context triple: [Operation Ripper, frontLineAdvance, advance toward the 38th parallel]
  • A. frontlineAdvance chosen
    Indicates a movement of military or conflict front lines forward into previously uncontrolled or enemy-held territory.
  • B. frontLine
    Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
  • C. frontLineFeature
    Indicates that the subject is a prominent or leading characteristic that stands out at the forefront relative to others.
  • D. frontLineDuring
    Indicates that an entity is positioned at or serves on the front line during a specified time or event.
  • E. frontLineStrength
    Indicates the level of combat capability or effectiveness of forces positioned at the front line in a conflict or operation.
  • 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_69f22497f91c8190afa7165bc900accd completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6953bafb88190a860e9c68a3dd4b2 completed May 3, 2026, 12:22 a.m.
PD Predicate disambiguation batch_69f690ed5d008190831cf8e44cce28af completed May 3, 2026, 12:03 a.m.
Created at: April 29, 2026, 8:13 p.m.