Triple
T18900659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justus |
E462330
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Justinus |
—
|
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: Justinus | Statement: [Justus, hasVariant, Justinus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Justinus Context triple: [Justus, hasVariant, Justinus]
-
A.
Justinus
chosen
Justinus is a Latin given name and surname historically borne by several early Christian writers and Roman figures, from which the name Justin is derived.
-
B.
Giustino
Giustino is a small village and comune in the Trentino region of northern Italy, situated in the Italian Alps.
-
C.
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.
-
D.
Marcianus
Marcianus was a late Roman imperial prince, known primarily as the son of Western Roman Emperor Anthemius.
-
E.
Anicius Julianus
Anicius Julianus was a member of the prominent late Roman Anicii family, known for its influential senatorial and political roles in the 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c5289ba48190a6825c4db2e5e48d |
completed | April 20, 2026, 6:18 a.m. |
Created at: April 10, 2026, 11:58 a.m.