Triple
T34129243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adversus Rhetoras |
E875376
|
entity |
| Predicate | hasCriticalStanceToward |
P3619
|
FINISHED |
| Object | professional rhetoricians |
—
|
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: professional rhetoricians | Statement: [Adversus Rhetoras, hasCriticalStanceToward, professional rhetoricians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriticalStanceToward Context triple: [Adversus Rhetoras, hasCriticalStanceToward, professional rhetoricians]
-
A.
editorialStance
Indicates the position, viewpoint, or bias an editor or publication adopts toward a subject, issue, or entity.
-
B.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
-
C.
hasAuthorialStance
Indicates that an entity expresses, embodies, or is associated with a particular author’s viewpoint, attitude, or perspective toward its subject matter.
-
D.
hasCriticism
chosen
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
E.
conflictStance
Indicates a party’s position, attitude, or alignment regarding a particular conflict or dispute.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 1, 2026, 1:53 a.m.