Triple

T20203049
Position Surface form Disambiguated ID Type / Status
Subject Dorian invasion E493271 entity
Predicate consequenceTraditionally P113484 FINISHED
Object destruction or abandonment of Mycenaean centers 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: destruction or abandonment of Mycenaean centers | Statement: [Dorian invasion, consequenceTraditionally, destruction or abandonment of Mycenaean centers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceTraditionally
Context triple: [Dorian invasion, consequenceTraditionally, destruction or abandonment of Mycenaean centers]
  • A. consequenceInText
    Indicates that one event, action, or state is presented in the text as a consequence or result of another.
  • B. consequenceOfInfluence
    Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
  • C. hasConsequence
    Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
  • D. significantEventConsequence
    Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
  • E. interpretiveConsequence chosen
    Indicates that one entity is a conclusion, implication, or interpretive outcome that follows from another entity.
  • 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_69da6269614c8190bb40475d9d477358 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66d8ec73c8190b630599c5ceb22ac completed April 20, 2026, 6:16 p.m.
PD Predicate disambiguation batch_69e55b14c9d8819095453d0504d9222f completed April 19, 2026, 10:45 p.m.
Created at: April 11, 2026, 11:38 p.m.