Triple
T8310825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy XV Caesarion as legitimate son of Julius Caesar |
E194585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical claim |
C24201
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical claim Context triple: [Ptolemy XV Caesarion as legitimate son of Julius Caesar, instanceOf, historical claim]
-
A.
historical myth
A historical myth is a widely held narrative about past events that blends factual history with legend, symbolism, or cultural interpretation, often shaping collective identity more than accurately recording what occurred.
-
B.
historical position
A historical position is a specific role, office, or status held by an individual within a past social, political, or cultural context, defined by its responsibilities, authority, and time period.
-
C.
historical material
Historical material is any primary or secondary source—such as documents, artifacts, recordings, or testimonies—created in or about the past that provides evidence for understanding historical events, contexts, and perspectives.
-
D.
historical topic
A historical topic is a specific subject, event, period, or theme from the past that is studied, analyzed, and interpreted to understand historical developments and their impact.
-
E.
historiographical construct
A historiographical construct is an interpretive framework or conceptual model that historians create to organize, explain, and give meaning to past events and processes.
- F. None of above. chosen
Provenance (1 batch)
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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:54 p.m.