Triple
T36385403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divus Iulius |
E896180
|
entity |
| Predicate | hasApotheosisType |
P196378
|
FINISHED |
| Object | state-sanctioned apotheosis |
—
|
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: state-sanctioned apotheosis | Statement: [Divus Iulius, hasApotheosisType, state-sanctioned apotheosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApotheosisType Context triple: [Divus Iulius, hasApotheosisType, state-sanctioned apotheosis]
-
A.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
B.
hasArchetype
Indicates that one entity serves as the original model, pattern, or prototype upon which another entity is based or conceptually derived.
-
C.
hasEpitomeBy
Indicates that something is represented, summarized, or exemplified by a particular epitome (a concise or quintessential representation of it).
-
D.
hasEponymType
Indicates that something is associated with or classified by a particular type of eponym (a name derived from a person).
-
E.
hasRevelationType
Indicates the specific kind or category of revelation associated with an entity or event.
- F. None of above. chosen
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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69fe2f066ac48190882c327b7e69e53f |
completed | May 8, 2026, 6:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.