Triple

T18859514
Position Surface form Disambiguated ID Type / Status
Subject Augusta Victoria of Hohenzollern E461271 entity
Predicate givenName P17 FINISHED
Object Viktoria 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: Viktoria | Statement: [Augusta Victoria of Hohenzollern, givenName, Viktoria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Viktoria
Context triple: [Augusta Victoria of Hohenzollern, givenName, Viktoria]
  • A. Viktoria chosen
    Viktoria is a feminine given name of Latin origin, commonly used in various European countries as a variant of "Victoria."
  • B. Viktorka
    Viktorka is the popular nickname of FC Viktoria Plzeň, a professional football club from Plzeň in the Czech Republic.
  • C. Vladimira
    Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
  • D. Vika
    Vika is a central neighborhood in Oslo, Norway, known for its waterfront location, cultural institutions, and proximity to the city’s business district.
  • E. Victoriei
    Victoriei is a major Bucharest Metro interchange station serving as an important transit hub in Romania’s capital city.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c05fb800819098951ec134a1fa2a completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:57 a.m.