Triple

T8977835
Position Surface form Disambiguated ID Type / Status
Subject Hubertus E214439 entity
Predicate relatedName P3889 FINISHED
Object Hubertusz E214439 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: Hubertusz | Statement: [Hubertus, relatedName, Hubertusz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hubertusz
Context triple: [Hubertus, relatedName, Hubertusz]
  • A. Hubert
    Hubert is a masculine given name of Germanic origin meaning "bright heart" or "shining intellect," historically borne by saints, nobles, and notable public figures.
  • B. Hubertus chosen
    Hubertus is a masculine given name of Germanic origin, commonly used in various European countries.
  • C. Henryk
    Henryk is a masculine given name of Germanic origin commonly used in Poland and other Central and Eastern European countries.
  • D. Ludwik
    Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
  • E. Thaddaeus
    Thaddaeus is a disciple of Jesus traditionally counted among the Twelve Apostles in Christian tradition, often identified with Jude the Apostle.
  • 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67a33c8481909125acf4b7f0a919 completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfd0afe9688190bdd66198ab31c2c7 completed April 3, 2026, 2:37 p.m.
Created at: March 30, 2026, 7:02 p.m.