Triple
T31414297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JCIO |
E801349
|
entity |
| Predicate | acceptsComplaintsFrom |
P91596
|
FINISHED |
| Object | members of the public |
—
|
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: members of the public | Statement: [JCIO, acceptsComplaintsFrom, members of the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsComplaintsFrom Context triple: [JCIO, acceptsComplaintsFrom, members of the public]
-
A.
handlesComplaintsOn
chosen
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
-
B.
complainedTo
Indicates that one entity expressed dissatisfaction, criticism, or a grievance directly to another entity.
-
C.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
D.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
-
E.
complaintsJurisdiction
Indicates that an authority or body has the legal power to receive, hear, and decide on complaints within a specified scope or area.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:42 p.m.