Triple

T19825536
Position Surface form Disambiguated ID Type / Status
Subject Gundisalvus of Amarante E476314 entity
Predicate givenName P17 FINISHED
Object Gundisalvus NE NERFINISHED

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: Gundisalvus | Statement: [Gundisalvus of Amarante, givenName, Gundisalvus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gundisalvus
Context triple: [Gundisalvus of Amarante, givenName, Gundisalvus]
  • A. Gundisalvus chosen
    Gundisalvus is a medieval Latin given name of Visigothic origin that later evolved into the Spanish name Gonzalo.
  • B. Gotarzes II
    Gotarzes II was a 1st-century AD king of the Parthian Empire known for his turbulent reign marked by internal dynastic struggles and conflicts over succession.
  • C. Saloninus
    Saloninus was a short-lived Roman imperial claimant of the 3rd century, briefly elevated as Caesar before being overthrown and killed during the Gallic Empire’s secession.
  • D. Dulo
    Dulo was the early medieval ruling dynasty of the Bulgars, traditionally associated with Khan Asparuh and the founding of the First Bulgarian Empire.
  • E. Gundicarius
    Gundicarius was a 5th-century king of the Burgundians, remembered for his role in the events later mythologized in the Nibelungen legends.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e656c9e7348190a569a40bd1fca6ba completed April 20, 2026, 4:39 p.m.
Created at: April 10, 2026, 1:50 p.m.