Triple

T3840621
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of the Franks E93440 entity
Predicate notableRuler P22 FINISHED
Object Clovis I E281739 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: Clovis I | Statement: [Kingdom of the Franks, notableRuler, Clovis I]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clovis I
Context triple: [Kingdom of the Franks, notableRuler, Clovis I]
  • A. Clovis
    Clovis is a small city in eastern New Mexico known as a regional hub for agriculture, rail transport, and nearby Cannon Air Force Base.
  • B. Clovis chosen
    Clovis is a masculine given name of Germanic origin, historically associated with early Frankish kings and related to names like Louis and Ludwig.
  • C. Clovis
    Clovis is a city in Fresno County, California, known as a gateway to the Sierra Nevada and for its historic Old Town district.
  • D. Gundobad
    Gundobad was a powerful Burgundian king and former Roman general who played a key role in the late Western Roman Empire’s politics and later ruled the Burgundian kingdom in Gaul.
  • E. Arnulf of Metz
    Arnulf of Metz was a 7th-century Frankish nobleman, bishop, and statesman regarded as a founding ancestor of the Carolingian line that produced Charlemagne.
  • 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_69aed96ce578819084ab16e3439976c9 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeeba1535c8190b36e2ab2d4514b54 completed March 9, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5627ebbc48190914b663bab5e2a82 completed March 14, 2026, 1:28 p.m.
Created at: March 9, 2026, 3:18 p.m.