Triple
T13770008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lollius |
E330854
|
entity |
| Predicate | hasPraenomenPattern |
P109316
|
FINISHED |
| Object | standard Roman praenomina for male members |
—
|
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: standard Roman praenomina for male members | Statement: [Lollius, hasPraenomenPattern, standard Roman praenomina for male members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPraenomenPattern Context triple: [Lollius, hasPraenomenPattern, standard Roman praenomina for male members]
-
A.
isPraenomenOf
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
B.
memberHasPraenomen
chosen
Indicates that a member is associated with or bears a specific praenomen (personal given name).
-
C.
hasSurnamePattern
Indicates that an entity’s surname follows or matches a specified structural or stylistic pattern.
-
D.
isPatronymicName
Indicates that a name is derived from a father’s or ancestor’s given name, typically signifying lineage or descent.
-
E.
praenomenOfEthnicity
Indicates that a given personal first name (praenomen) is characteristic of, or associated with, a particular ethnicity.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0233ecc48190b934f085d2501eb1 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.