Triple
T18119505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Fabian |
E433695
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Fabianus |
—
|
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: Fabianus | Statement: [Pope Fabian, alsoKnownAs, Fabianus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fabianus Context triple: [Pope Fabian, alsoKnownAs, Fabianus]
-
A.
Fabianus
chosen
Fabianus is an ancient Roman family name (nomen) associated with members of the gens Fabia.
-
B.
Florianus
Florianus was a short-reigning Roman emperor of the 3rd century, known primarily for his brief and turbulent rule during the Crisis of the Third Century.
-
C.
Firminus
Firminus is a Latin masculine given name, historically used in early Christian and medieval contexts and related to names like Firmin.
-
D.
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.
-
E.
Vibulanus
Vibulanus is a cognomen used by members of the ancient Roman patrician gens Fabia, distinguishing a particular branch of that family.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd843e88190abbc173dbc9b450a |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.