Triple

T31183776
Position Surface form Disambiguated ID Type / Status
Subject Lydians E794979 entity
Predicate afterConquestBecame P32946 FINISHED
Object satrapy of the Achaemenid Empire 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: satrapy of the Achaemenid Empire | Statement: [Lydians, afterConquestBecame, satrapy of the Achaemenid Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: afterConquestBecame
Context triple: [Lydians, afterConquestBecame, satrapy of the Achaemenid Empire]
  • A. afterConquest
    Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
  • B. afterConquestBy chosen
    Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
  • C. afterConquestName
    Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
  • D. convertedAfterConquest
    Indicates that one entity underwent conversion (typically religious or cultural) as a direct consequence of being conquered by another entity.
  • E. conqueredIn
    Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
  • 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_69f224d675d08190957198068e440422 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6d0d46aec819091edf97324d793ac completed May 3, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69f6cfe2183481908ae4e85a59c66f69 completed May 3, 2026, 4:32 a.m.
Created at: April 29, 2026, 9:08 p.m.