Triple
T28074618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honoria |
E709498
|
entity |
| Predicate | interpretedByCriticsAs |
P60346
|
FINISHED |
| Object | patriarchal feminine ideal |
—
|
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: patriarchal feminine ideal | Statement: [Honoria, interpretedByCriticsAs, patriarchal feminine ideal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretedByCriticsAs Context triple: [Honoria, interpretedByCriticsAs, patriarchal feminine ideal]
-
A.
isNotedByCriticsFor
chosen
Indicates that something has been recognized and highlighted by critics specifically for a particular quality, feature, or aspect.
-
B.
alsoCalledByCritics
Indicates that critics refer to the same entity by an alternative name or label.
-
C.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
D.
typeOfCriticism
Indicates that one entity is a specific kind or category of criticism directed at another entity or subject.
-
E.
famousCritique
Indicates that one entity is a well-known critical assessment, review, or commentary about 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 27, 2026, 8:48 p.m.