Triple

T588401
Position Surface form Disambiguated ID Type / Status
Subject Julian Amery E17211 entity
Predicate givenName P17 FINISHED
Object Julian 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: Julian | Statement: [Julian Amery, givenName, Julian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Julian
Context triple: [Julian Amery, givenName, Julian]
  • A. Julian chosen
    Julian is a masculine given name of Latin origin, commonly used in many English-speaking and European countries.
  • B. Flavius
    Flavius is a common Roman praenomen and family name frequently borne by late Roman emperors and officials, including Romulus Augustulus.
  • C. Julius
    Julius is the family name (nomen) of the ancient Roman Julian clan, most famously borne by figures such as Gaius Julius Caesar and later adopted by emperors like Tiberius as part of their imperial identity.
  • D. Julius
    Julius is the first given name of J. Robert Oppenheimer, the American theoretical physicist known as the "father of the atomic bomb."
  • E. Claudiu
    Claudiu is a Romanian given name derived from the ancient Roman name Claudius.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49b9d1e68819096a9b5e7b2e83d6e completed March 1, 2026, 8:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69a55a734f6c8190a141dafc03dd2e77 completed March 2, 2026, 9:37 a.m.
Created at: March 1, 2026, 7:33 p.m.