Triple
T2266654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidcup |
E50159
|
entity |
| Predicate | localAuthorityDistrictCode |
P37557
|
FINISHED |
| Object | E09000004 |
—
|
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: E09000004 | Statement: [Sidcup, localAuthorityDistrictCode, E09000004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localAuthorityDistrictCode Context triple: [Sidcup, localAuthorityDistrictCode, E09000004]
-
A.
localAuthorityArea
Indicates that one entity is a geographic or administrative area governed or managed by a specified local authority.
-
B.
localAuthorityAreaCode
Indicates the specific administrative or jurisdictional area code assigned by a local authority that is associated with the subject entity.
-
C.
sourceLocalAuthorityArea
Indicates the local authority area from which something originates, is administered, or is sourced.
-
D.
localElectoralArea
Indicates a relationship where a geographic or administrative region is designated as a specific local electoral area for voting or representation purposes.
-
E.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abc2e97eb0819084acb26cfa4e3946 |
completed | March 7, 2026, 6:17 a.m. |
Created at: March 4, 2026, 7:48 p.m.