Triple
T34210001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquilia Severa |
E877626
|
entity |
| Predicate | praenomenOrCognomen |
P50475
|
FINISHED |
| Object | Severa |
—
|
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: Severa | Statement: [Aquilia Severa, praenomenOrCognomen, Severa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: praenomenOrCognomen Context triple: [Aquilia Severa, praenomenOrCognomen, Severa]
-
A.
praenomenOrNomen
Indicates that the related name element functions either as a personal given name (praenomen) or as a family/clan name (nomen) within a naming system.
-
B.
cognomenOf
chosen
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
C.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
-
D.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
E.
isPraenomenOf
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
- F. None of above.
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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71054384481908897507876233248 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.