Triple
T14856940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Tamworth |
E349381
|
entity |
| Predicate | ONSCode |
P73848
|
FINISHED |
| Object | 41UD |
—
|
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: 41UD | Statement: [Borough of Tamworth, ONSCode, 41UD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ONSCode Context triple: [Borough of Tamworth, ONSCode, 41UD]
-
A.
hasONSCode
chosen
Indicates that an entity is associated with a specific code assigned by the Office for National Statistics (ONS) for identification or classification purposes.
-
B.
NOCCode
Indicates the standardized occupational classification code assigned to a job or role within the National Occupational Classification system.
-
C.
isOfficialCodeFor
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
D.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
E.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44458ec8190be295a95f5daab14 |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.