Triple

T1167707
Position Surface form Disambiguated ID Type / Status
Subject Julian E24836 entity
Predicate derivedFrom P909 FINISHED
Object Iulianus E24836 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: Iulianus | Statement: [Julian, derivedFrom, Iulianus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Iulianus
Context triple: [Julian, derivedFrom, Iulianus]
  • A. Julian chosen
    Julian is a masculine given name of Latin origin, commonly used in many English-speaking and European countries.
  • B. Carinus
    Carinus was a Roman emperor of the late 3rd century who ruled during the Crisis of the Third Century and was ultimately defeated by Diocletian.
  • C. Claudiianus
    Claudiianus is a Latin-derived personal name likely associated with or stemming from the Roman family name Claudius.
  • D. Claudius Pompeianus
    Claudius Pompeianus was a prominent 2nd-century Roman general and senator, son-in-law of Emperor Marcus Aurelius, who played a key military role during the Marcomannic Wars.
  • E. Flavius
    Flavius is a common Roman praenomen and family name frequently borne by late Roman emperors and officials, including Romulus Augustulus.
  • 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_69a494082a7c819095004f423f294a64 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bccef84481908864e819884af86c completed March 1, 2026, 10:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac8a0646388190b440451d786db04c completed March 7, 2026, 8:26 p.m.
Created at: March 1, 2026, 7:45 p.m.