Triple
T8310827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemy XV Caesarion as legitimate son of Julius Caesar |
E194585
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political propaganda claim |
C24203
|
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: political propaganda claim Context triple: [Ptolemy XV Caesarion as legitimate son of Julius Caesar, instanceOf, political propaganda claim]
-
A.
propaganda post
A propaganda post is a piece of content designed to influence opinions or behaviors by selectively presenting information, often using emotional appeals, bias, or misinformation to promote a particular agenda.
-
B.
political proclamation
A political proclamation is an official public statement issued by a governing authority or political leader to declare intentions, policies, positions, or significant decisions to the populace.
-
C.
propaganda poster
A propaganda poster is a visually striking, often simplified and emotionally charged printed image or design created to influence public opinion or behavior in support of a particular political, ideological, or social agenda.
-
D.
wartime propaganda campaign
A wartime propaganda campaign is a coordinated effort by a government or organization to shape public opinion, morale, and behavior during armed conflict through controlled messages, media, and symbolism.
-
E.
propaganda newspaper
A propaganda newspaper is a periodical publication designed primarily to disseminate biased or misleading information in order to shape public opinion and advance a specific political, ideological, or organizational agenda.
- 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.