Triple
T31077368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcius family |
E792001
|
entity |
| Predicate | associatedCognomen |
P50475
|
FINISHED |
| Object | Cato |
E871124
|
NE 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: Cato | Statement: [Porcius family, associatedCognomen, Cato]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCognomen Context triple: [Porcius family, associatedCognomen, Cato]
-
A.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
B.
cognomenOf
chosen
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
C.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
D.
surnameAssociatedWithField
Indicates that a particular surname is commonly linked or connected to a specific professional, academic, or activity-related field.
-
E.
etymologyOfCognomen
Indicates that one term specifies the linguistic origin or derivation of a particular cognomen (surname or family name).
- F. None of above.
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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a292b23e16c819083a3d342fea5a473 |
completed | June 10, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:02 p.m.