Triple

T22158300
Position Surface form Disambiguated ID Type / Status
Subject Aurélien E547598 entity
Predicate hasRelatedName P3889 FINISHED
Object Aurelian 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: Aurelian | Statement: [Aurélien, hasRelatedName, Aurelian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aurelian
Context triple: [Aurélien, hasRelatedName, Aurelian]
  • A. Aurelian chosen
    Aurelian was a 3rd-century Roman emperor known for restoring the empire’s unity and strengthening its frontiers through military reforms and administrative reorganization.
  • B. Aurelios
    Aurelios is a variant form of the name Aurelius, historically associated with ancient Roman figures and Latin origins.
  • C. Aemilian
    Aemilian was a short-lived Roman emperor of the 3rd century whose brief reign occurred amid the political instability and military upheavals of the Roman civil wars.
  • D. Vetranio
    Vetranio was a 4th-century Roman general who briefly ruled as a usurper emperor in the Balkans before abdicating in favor of Constantius II.
  • E. Jovinus
    Jovinus was a Roman usurper who briefly claimed the imperial title in Gaul during the early 5th century Western Roman Empire.
  • 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_69e11e3b52088190ad5df386d01eb2fb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12a2b5b10819090630fbadacb67af completed April 28, 2026, 9:44 p.m.
Created at: April 16, 2026, 8:33 p.m.