Triple
T7914408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julien |
E183782
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Julienus |
E704416
|
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: Julienus | Statement: [Julien, hasCognate, Julienus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Julienus Context triple: [Julien, hasCognate, Julienus]
-
A.
Julienus
chosen
Julienus is a Latinized variant of the given name Julien, historically used in Roman and medieval contexts.
-
B.
Lollius
Lollius was the Roman gens (family line) to which the aristocratic woman and briefly reigning empress Lollia Paulina belonged.
-
C.
Albinus
Albinus is an alternative name for Alcuin of York, the influential 8th-century Anglo-Saxon scholar, theologian, and advisor at Charlemagne’s court.
-
D.
Julius Argentarius
Julius Argentarius was a wealthy Byzantine financier and patron active in 6th-century Ravenna, known for funding major church constructions such as the Basilica of San Vitale.
-
E.
Aelius
Aelius is an ancient Roman family name (nomen) associated with several notable figures of the Roman Empire, including emperors and high-ranking officials.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a759b548190af2e2aa0705d7051 |
completed | March 31, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc563cb0a081909ed43ff45a8a1fa0 |
completed | March 31, 2026, 11:18 p.m. |
Created at: March 30, 2026, 5:04 p.m.