Triple
T21957046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cléonte |
E542217
|
entity |
| Predicate | contrastsWithTheme |
P7994
|
FINISHED |
| Object | social pretension |
—
|
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: social pretension | Statement: [Cléonte, contrastsWithTheme, social pretension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contrastsWithTheme Context triple: [Cléonte, contrastsWithTheme, social pretension]
-
A.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
B.
themeContrast
chosen
Indicates a relationship where two themes are compared or opposed to highlight their differences or tension.
-
C.
dramaticContrastWith
Indicates that one entity is presented in a way that sharply emphasizes differences in tone, style, or impact when compared with another entity.
-
D.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
-
E.
usesThemeBy
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1244108948190a08e6966e55c4acd |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.