Triple
T34420102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatissime Pater |
E883501
|
entity |
| Predicate | paterMeaning |
P178928
|
FINISHED |
| Object | father |
—
|
LITERAL 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: father | Statement: [Beatissime Pater, paterMeaning, father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paterMeaning Context triple: [Beatissime Pater, paterMeaning, father]
-
A.
paterPatratusRole
Indicates the role of someone formally appointed as pater patratus, the official representative empowered to speak or act on behalf of a group in a ritual or diplomatic context.
-
B.
patriarch
Indicates a relationship where one entity serves as the male head or senior father-figure authority over a family, clan, or lineage of other entities.
-
C.
motherFather
Indicates that the two entities are the biological parents (mother and father) of a child or offspring.
-
D.
hasMeaningAsPatronymicMarker
Indicates that something functions as a marker showing that a name is derived from a father’s or ancestor’s personal name (i.e., it serves as a patronymic indicator).
-
E.
patriarchTitle
Indicates that one entity holds the role or title of patriarch in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f719458378819081725f544efb1173 |
completed | May 3, 2026, 9:45 a.m. |
Created at: May 1, 2026, 2 a.m.