Triple
T36066617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurelius |
E1043248
|
entity |
| Predicate | hasCognomenForm |
P50475
|
FINISHED |
| Object | Aurelianus |
E762121
|
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: Aurelianus | Statement: [Aurelius, hasCognomenForm, Aurelianus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCognomenForm Context triple: [Aurelius, hasCognomenForm, Aurelianus]
-
A.
memberHasCognomen
Indicates that a member is associated with or bears a specific cognomen (surname or additional family name).
-
B.
cognomenOf
chosen
Indicates that one entity is the cognomen (surname or family name) of another entity.
-
C.
hasGentilicForm
Indicates that one term is the gentilic (demonym or adjectival form denoting origin or affiliation) derived from or associated with another term.
-
D.
hasSeptSurname
Indicates that an entity bears a surname associated with a particular sept (a family subgroup or clan division).
-
E.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38cbab52648190803a1e6414443af7 |
completed | June 22, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.