Triple

T9045663
Position Surface form Disambiguated ID Type / Status
Subject George E216747 entity
Predicate isCognateOf P2527 FINISHED
Object Gheorghe E237057 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: Gheorghe | Statement: [George, isCognateOf, Gheorghe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gheorghe
Context triple: [George, isCognateOf, Gheorghe]
  • A. Gheorghe chosen
    Gheorghe is a common Romanian male given name of Greek origin, equivalent to George in English.
  • B. Gheorghe Buzdugan
    Gheorghe Buzdugan is a Romanian engineer and academic known for his contributions to electrical engineering and higher education in Romania.
  • C. Gheorghiu
    Gheorghiu is a Romanian surname most prominently associated with celebrated operatic soprano Angela Gheorghiu.
  • D. Timotei
    Timotei is a given name, commonly used in Eastern European and Scandinavian countries, that is related to the name Timofey.
  • E. Kogălniceanu
    Kogălniceanu was a prominent 19th-century Romanian statesman, historian, and liberal reformer who played a key role in the modernization and political unification of the Romanian principalities.
  • 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_69ca83d22d488190adbce5e020e9cd1d completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc6b148b188190814d64acae493634 completed April 1, 2026, 12:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffdb868e48190b9d193025cb5b9a2 completed April 3, 2026, 5:49 p.m.
Created at: March 30, 2026, 7:09 p.m.