Triple
T28772887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciceronian rhetorical corpus |
E726458
|
entity |
| Predicate | articulatesTheoryOf |
P38287
|
FINISHED |
| Object | oratory |
—
|
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: oratory | Statement: [Ciceronian rhetorical corpus, articulatesTheoryOf, oratory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articulatesTheoryOf Context triple: [Ciceronian rhetorical corpus, articulatesTheoryOf, oratory]
-
A.
presentsTheory
chosen
Indicates that one entity formally puts forward or explains a theory to another entity or audience.
-
B.
governingTheory
Indicates that one entity serves as the primary theoretical framework or principle that explains, constrains, or directs the behavior, interpretation, or operation of another entity.
-
C.
developsTheory
Indicates that one entity formulates, elaborates, or advances a theoretical framework or explanation concerning another entity.
-
D.
reflectsTheoryOf
Indicates that one entity embodies, expresses, or is based on the theoretical framework, principles, or assumptions developed by another entity.
-
E.
hasTheory
Indicates that an entity possesses, is associated with, or is characterized by a particular theory.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:16 a.m.