Triple

T5565177
Position Surface form Disambiguated ID Type / Status
Subject Saite political renaissance E145862 entity
Predicate hasMilitaryEvent P2107 FINISHED
Object Egyptian campaigns in the Levant 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: Egyptian campaigns in the Levant | Statement: [Saite political renaissance, hasMilitaryEvent, Egyptian campaigns in the Levant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMilitaryEvent
Context triple: [Saite political renaissance, hasMilitaryEvent, Egyptian campaigns in the Levant]
  • A. hasHistoricalEvent chosen
    Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
  • B. hasMilitarySignificance
    Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
  • C. wasMilitarizedDuring
    Indicates that an entity transitioned to or adopted a military character, role, or control during a specified time period or event.
  • D. militaryActivity
    Indicates that an entity is engaged in, associated with, or affected by actions, operations, or preparations conducted by armed forces.
  • E. hasMilitarySignificanceSince
    Indicates that something has held military importance or strategic value starting from a specified point in time.
  • 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_69c008fdae24819081aa002ad99cd966 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c02033cc308190895f13454c57f452 completed March 22, 2026, 5 p.m.
PD Predicate disambiguation batch_69c01b12826c8190969a584d0f53aa44 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:36 p.m.