Triple
T835966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British press |
E18068
|
entity |
| Predicate | criticisedFor |
P805
|
FINISHED |
| Object | intrusion into 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: intrusion into privacy | Statement: [British press, criticisedFor, intrusion into privacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criticisedFor Context triple: [British press, criticisedFor, intrusion into privacy]
-
A.
criticizedFor
chosen
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
B.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
C.
criticizesSource
Indicates that one entity expresses disapproval of, or negative judgment about, the content, behavior, or credibility of another entity that is treated as a source.
-
D.
derogatesFrom
Indicates that one entity diminishes, belittles, or detracts from the value, reputation, or importance of another entity.
-
E.
criticalReception
Indicates how a work, performance, or product is evaluated and responded to by critics or professional reviewers.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abce08348190b716e3ce5a638f99 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7c7df881909c539c3ab8ff0367 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.