Triple
T4735842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrity magazines |
E105123
|
entity |
| Predicate | oftenCriticizedFor |
P53756
|
FINISHED |
| Object | invasion of privacy |
—
|
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: invasion of privacy | Statement: [Celebrity magazines, oftenCriticizedFor, invasion of privacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCriticizedFor Context triple: [Celebrity magazines, oftenCriticizedFor, invasion of privacy]
-
A.
sometimesCriticizedFor
chosen
Indicates that an entity is on occasion the target of criticism for a particular reason, behavior, or attribute.
-
B.
criticizedFor
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
C.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
D.
criticizedConstruct
Indicates that one entity expressed disapproval or negative judgment about another entity’s constructed work, idea, or creation.
-
E.
aimsToCritique
Indicates an intention to analyze and point out faults, limitations, or weaknesses in something.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd648148b48190ae30631115339ba1 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.