Triple

T24760144
Position Surface form Disambiguated ID Type / Status
Subject Sasanian invasion of the Levant E619412 entity
Predicate territoryOverrun P77284 FINISHED
Object Byzantine Palestine NE NERFINISHED

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: Byzantine Palestine | Statement: [Sasanian invasion of the Levant, territoryOverrun, Byzantine Palestine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: territoryOverrun
Context triple: [Sasanian invasion of the Levant, territoryOverrun, Byzantine Palestine]
  • A. territorialConsequence
    Indicates the resulting change or effect on territorial control, boundaries, or status that follows from a particular event, action, or condition.
  • B. heldTerritory
    Indicates that one entity maintained control or possession over a specific territory or geographic area.
  • C. gainedTerritory chosen
    Indicates that one entity has acquired control over additional land or area from another entity or from a neutral state.
  • D. territorialAmbition
    Indicates a desire or intent by one entity to expand its control, ownership, or influence over additional geographic areas or territories.
  • E. territorialBehavior
    Indicates a relationship where an entity actively defends or asserts control over a specific area or domain against others.
  • 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_69e2fabbea94819092ed41348909622f completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 4:27 a.m.