Triple

T14715058
Position Surface form Disambiguated ID Type / Status
Subject The Last Liberator E345654 entity
Predicate hasHistoricalBackdrop P1409 FINISHED
Object yes 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: yes | Statement: [The Last Liberator, hasHistoricalBackdrop, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricalBackdrop
Context triple: [The Last Liberator, hasHistoricalBackdrop, yes]
  • A. hasHistoricalSection
    Indicates that something includes a dedicated part or segment that presents historical information or context.
  • B. hasHistoricalContext chosen
    Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
  • C. hasHistoricity
    Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
  • D. hasHistoricalSuperstrate
    Indicates that one language or culture has served as a historically dominant external influence shaping another language or culture, typically through contact, conquest, or prestige.
  • E. hasHistoricFeatures
    Indicates that something possesses characteristics, elements, or attributes of historical significance.
  • 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_69d822e5911c8190ba589f957dbd9ba7 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb98513b081908b230f6ac79c72ad completed April 14, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69de657e174481909da0437556334a04 completed April 14, 2026, 4:04 p.m.
Created at: April 10, 2026, 1:29 a.m.