Triple

T5811256
Position Surface form Disambiguated ID Type / Status
Subject Aurel E128871 entity
Predicate hasVariant P455 FINISHED
Object Aurél E128871 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: Aurél | Statement: [Aurel, hasVariant, Aurél]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aurél
Context triple: [Aurel, hasVariant, Aurél]
  • A. Aurel chosen
    Aurel is a masculine given name most notably borne by the Hungarian-British archaeologist and explorer Aurel Stein, famed for his expeditions along the Silk Road.
  • B. Alexandru
    Alexandru is a masculine given name of Greek origin, commonly used in Eastern Europe and derived from the name Alexander.
  • C. Béla
    Béla was a common medieval Hungarian royal given name borne by several kings, most notably Béla IV of Hungary.
  • D. Desiderius
    Desiderius was the final king of the Lombards, whose defeat by Charlemagne in the 8th century marked the end of the Lombard Kingdom in Italy.
  • E. Vasile
    Vasile is a masculine given name, primarily used in Romania and Moldova, derived from the Greek name Basil (Basileios), meaning "kingly" or "royal."
  • 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_69c0084788848190bcf71f6bc5d71597 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02b538cd08190a7dac378898059b9 completed March 22, 2026, 5:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c09844f0b881908d4165e550f75d47 completed March 23, 2026, 1:32 a.m.
Created at: March 22, 2026, 3:52 p.m.