Triple
T1110251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent and Sussex Courier |
E25577
|
entity |
| Predicate | publishingPurpose |
P24455
|
FINISHED |
| Object | inform local communities |
—
|
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: inform local communities | Statement: [Kent and Sussex Courier, publishingPurpose, inform local communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishingPurpose Context triple: [Kent and Sussex Courier, publishingPurpose, inform local communities]
-
A.
publishesFor
Indicates that one entity issues, releases, or makes content publicly available on behalf of, or in service of, another entity.
-
B.
publicationType
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
C.
publishingModel
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
D.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
E.
publishingOrganization
Indicates the organization responsible for issuing or making the referenced work publicly available.
- F. None of above. chosen
Provenance (4 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bbd7ff1881908c943ecdfea59e81 |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:43 p.m.