Triple
T18218902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Press Complaints Commission |
E436239
|
entity |
| Predicate | complaintsProcess |
P20807
|
FINISHED |
| Object | free to complainants |
—
|
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: free to complainants | Statement: [Press Complaints Commission, complaintsProcess, free to complainants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complaintsProcess Context triple: [Press Complaints Commission, complaintsProcess, free to complainants]
-
A.
complaintsProcedure
chosen
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
B.
handlesComplaintsOn
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
-
C.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
D.
concernsProcess
Indicates that something is about, related to, or focused on a particular process or sequence of operations.
-
E.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47926988190802c00b074cdc696 |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.