Triple
T11493199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulphan |
E272466
|
entity |
| Predicate | hasLocalAuthorityDistrictCode |
P37557
|
FINISHED |
| Object | E06000034 |
—
|
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: E06000034 | Statement: [Bulphan, hasLocalAuthorityDistrictCode, E06000034]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalAuthorityDistrictCode Context triple: [Bulphan, hasLocalAuthorityDistrictCode, E06000034]
-
A.
localAuthorityDistrictCode
chosen
Indicates the specific local authority district to which an entity is administratively assigned, represented by its official code.
-
B.
hasLocalGovernmentAreaCode
Indicates that an entity is associated with a specific local government area identified by a particular code.
-
C.
hasLocalGovernmentCode
Indicates that an entity is associated with a specific code assigned by a local government authority for identification or administrative purposes.
-
D.
localAuthorityArea
Indicates that one entity is a geographic or administrative area governed or managed by a specified local authority.
-
E.
currentLocalAuthority
Indicates that one entity is the local governing authority that currently has jurisdiction over another entity 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85ddffdf88190a00e94ad5b8b91a5 |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.