Triple
T15849345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deification of Julius Caesar |
E384294
|
entity |
| Predicate | providedTitleFor |
P47620
|
FINISHED |
| Object | Divi filius |
—
|
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: Divi filius | Statement: [deification of Julius Caesar, providedTitleFor, Divi filius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedTitleFor Context triple: [deification of Julius Caesar, providedTitleFor, Divi filius]
-
A.
providedTitle
chosen
Indicates that one entity has supplied or assigned a specific title or designation to another entity.
-
B.
receivedTitle
Indicates that an entity has been formally granted or awarded a specific title or honor.
-
C.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
commonTitle
Indicates that two or more entities share the same title or designation.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14caa3fa481909bd01f3b901d7716 |
completed | April 16, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.