Triple
T13761499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Roman nomen |
E330619
|
entity |
| Predicate | example |
P1259
|
FINISHED |
| Object |
Fabianus
Fabianus is an ancient Roman family name (nomen) associated with members of the gens Fabia.
|
E1060132
|
NE FINISHED |
How this triple was built (4 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: Fabianus | Statement: [Ancient Roman nomen, example, Fabianus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fabianus Context triple: [Ancient Roman nomen, example, Fabianus]
-
A.
Firminus
Firminus is a Latin masculine given name, historically used in early Christian and medieval contexts and related to names like Firmin.
-
B.
Severinus
Severinus is a Latin-origin given name historically borne by several early Christian saints and figures, and is cognate with the Scandinavian name Søren.
-
C.
Tyrannius Rufinus
Tyrannius Rufinus was a 4th–5th century Christian theologian and translator, best known for rendering Greek theological works, including those of Origen, into Latin.
-
D.
Cassianus
Cassianus is the Latin name of Saint Cassian of Imola, an early Christian martyr and teacher venerated in the Catholic Church.
-
E.
Quintianus
Quintianus is a Roman cognomen derived from the praenomen Quintus, typically indicating familial or ancestral association with someone bearing that name.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Fabianus Triple: [Ancient Roman nomen, example, Fabianus]
Generated description
Fabianus is an ancient Roman family name (nomen) associated with members of the gens Fabia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Fabianus Target entity description: Fabianus is an ancient Roman family name (nomen) associated with members of the gens Fabia.
-
A.
Firminus
Firminus is a Latin masculine given name, historically used in early Christian and medieval contexts and related to names like Firmin.
-
B.
Severinus
Severinus is a Latin-origin given name historically borne by several early Christian saints and figures, and is cognate with the Scandinavian name Søren.
-
C.
Tyrannius Rufinus
Tyrannius Rufinus was a 4th–5th century Christian theologian and translator, best known for rendering Greek theological works, including those of Origen, into Latin.
-
D.
Cassianus
Cassianus is the Latin name of Saint Cassian of Imola, an early Christian martyr and teacher venerated in the Catholic Church.
-
E.
Quintianus
Quintianus is a Roman cognomen derived from the praenomen Quintus, typically indicating familial or ancestral association with someone bearing that name.
- F. None of above. chosen
Provenance (5 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02250f4881908d5193b3d5d25844 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a8606dbc8190b0f7c38583986141 |
completed | May 3, 2026, 7:56 p.m. |
| NEDg | Description generation | batch_69f7ac4f847c8190ab8be535e5399c79 |
completed | May 3, 2026, 8:13 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f7acdf70f8819092700c7b6b619d13 |
completed | May 3, 2026, 8:15 p.m. |
Created at: April 9, 2026, 10:09 p.m.