Triple
T29832932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Borough of Wigan |
E757574
|
entity |
| Predicate | statusGrantedIn |
P28722
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [County Borough of Wigan, statusGrantedIn, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusGrantedIn Context triple: [County Borough of Wigan, statusGrantedIn, 1889]
-
A.
statusGrantedOn
Indicates the date or time at which a particular status was officially conferred or became effective for an entity.
-
B.
grantedStatus
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
C.
grantedIn
chosen
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
D.
mintStatusGranted
Indicates that an entity has been officially authorized or approved to mint (create or issue) something, such as tokens, assets, or items.
-
E.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 5:35 p.m.