Triple
T31950029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Discourse Intended to Commemorate the Discovery of America by Christopher Columbus |
E815754
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical oration |
C17154
|
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 oration Context triple: [A Discourse Intended to Commemorate the Discovery of America by Christopher Columbus, instanceOf, historical oration]
-
A.
commemorative oration
chosen
A commemorative oration is a formal speech delivered to honor, celebrate, or memorialize a person, group, event, or ideal, often highlighting shared values and collective memory.
-
B.
humanist oration
A humanist oration is a formal, rhetorically crafted speech rooted in classical models that celebrates human dignity, learning, and civic virtue while persuading an audience through reasoned argument and eloquent expression.
-
C.
Attic oratory
Attic oratory is the classical Athenian tradition of public speaking and rhetorical practice, exemplified by 5th–4th century BCE speakers whose speeches became foundational models for later rhetoric.
-
D.
early Christian oratory
Early Christian oratory is the practice of persuasive religious speech and preaching in the first centuries of Christianity, used to teach doctrine, inspire faith, and shape communal identity.
-
E.
historical assembly
A historical assembly is a formally organized gathering of people in the past, convened at a specific time and place to deliberate, decide, or legislate on matters of public, political, or social importance.
- F. None of above.
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:07 a.m.