Triple
T36882011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintilius |
E911504
|
entity |
| Predicate | cognomenPattern |
P97319
|
FINISHED |
| Object | formed from a praenomen plus suffix -ilius |
—
|
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: formed from a praenomen plus suffix -ilius | Statement: [Quintilius, cognomenPattern, formed from a praenomen plus suffix -ilius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cognomenPattern Context triple: [Quintilius, cognomenPattern, formed from a praenomen plus suffix -ilius]
-
A.
cognomenOf
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
B.
etymologyOfCognomen
chosen
Indicates that one term specifies the linguistic origin or derivation of a particular cognomen (surname or family name).
-
C.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
D.
memberHasCognomen
Indicates that a member is associated with or bears a specific cognomen (surname or additional family name).
-
E.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6aba048190b23406b692bbf9fa |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.