Triple
T9462252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Unrat |
E228175
|
entity |
| Predicate | targetOfCritique |
P56725
|
FINISHED |
| Object | bourgeois double standards |
—
|
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: bourgeois double standards | Statement: [Professor Unrat, targetOfCritique, bourgeois double standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetOfCritique Context triple: [Professor Unrat, targetOfCritique, bourgeois double standards]
-
A.
aimsToCritique
Indicates an intention to analyze and point out faults, limitations, or weaknesses in something.
-
B.
goalOfCritique
Indicates that a critique is directed toward achieving or serving a particular goal or purpose.
-
C.
criticObjective
chosen
Indicates that an entity serves as the target or focus of a critic’s evaluation, commentary, or judgment.
-
D.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
E.
usedToCritique
Indicates that something is employed as a means to analyze, evaluate, or express disapproval of something else.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcd9794819093c392489d4efbe9 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.