Triple

T14148325
Position Surface form Disambiguated ID Type / Status
Subject Lajos Kossuth E350609 entity
Predicate familyName P18 FINISHED
Object Kossuth E350609 NE 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: Kossuth | Statement: [Lajos Kossuth, familyName, Kossuth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kossuth
Context triple: [Lajos Kossuth, familyName, Kossuth]
  • A. Lajos Kossuth chosen
    Lajos Kossuth was a 19th-century Hungarian lawyer, journalist, and statesman who became a leading figure of the 1848–49 revolution and a symbol of the struggle for Hungarian independence.
  • B. Ferenc Neumann
    Ferenc Neumann, better known by his pen name Ferenc Molnár, was a prominent early 20th-century Hungarian playwright and novelist whose works, such as "Liliom," achieved international acclaim.
  • C. Frigyes
    Frigyes is a Hungarian masculine given name, notably borne by the influential mathematician Frigyes Riesz.
  • D. Miklós
    Miklós is a Hungarian masculine given name, equivalent to Nicholas in English.
  • E. Andrássy
    Andrássy is a prominent Hungarian noble family name historically associated with influential statesmen and aristocrats in the Austro-Hungarian Empire.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d827865f608190b311820428ae027b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61237ef481909374c1f68a2370b7 completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf7e86820819099d6e3d3d4229f0d completed May 7, 2026, 8:36 p.m.
Created at: April 10, 2026, 12:55 a.m.