Triple

T9675057
Position Surface form Disambiguated ID Type / Status
Subject Gheorghe Avramescu E234125 entity
Predicate familyName P18 FINISHED
Object Avramescu E234125 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: Avramescu | Statement: [Gheorghe Avramescu, familyName, Avramescu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Avramescu
Context triple: [Gheorghe Avramescu, familyName, Avramescu]
  • A. Avramescu chosen
    Avramescu is a Romanian surname most notably associated with Gheorghe Avramescu, a Romanian general during World War II.
  • B. Dumitrescu
    Dumitrescu is a Romanian surname borne by numerous notable figures in fields such as politics, the military, sports, and the arts.
  • C. Timotei
    Timotei is a given name, commonly used in Eastern European and Scandinavian countries, that is related to the name Timofey.
  • D. Nicușor
    Nicușor is a Romanian masculine given name, often used as a diminutive or affectionate form of Nicolae.
  • E. Sergiu
    Sergiu is a masculine given name of Romanian origin, notably borne by the renowned conductor Sergiu Celibidache.
  • 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_69ca848f55e48190b3f67252571c3d45 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9c6d6dd48190a77c486337a58cb6 completed April 1, 2026, 10:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69d18a30883081909e8f70225b6ee820 completed April 4, 2026, 10:01 p.m.
Created at: March 30, 2026, 8:15 p.m.