Triple
T30335487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G82 postcode district |
E771607
|
entity |
| Predicate | servesCouncilArea |
P121591
|
FINISHED |
| Object | West Dunbartonshire Council |
—
|
NE NERFINISHED |
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: West Dunbartonshire Council | Statement: [G82 postcode district, servesCouncilArea, West Dunbartonshire Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCouncilArea Context triple: [G82 postcode district, servesCouncilArea, West Dunbartonshire Council]
-
A.
servesGovernmentDistrict
chosen
Indicates that an entity provides official services or representation to a specific government district.
-
B.
servedDistrict
Indicates that an entity has provided official service or representation to a particular district.
-
C.
isCityCouncilArea
Indicates that a given geographic or administrative region functions as a city council jurisdiction or area of authority.
-
D.
servedLocalGovernmentArea
Indicates that an entity has provided official service, representation, or duties within a specified local government area.
-
E.
associatedWithCouncilArea
Indicates that an entity has a formal or contextual relationship with a specific council (administrative) 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 29, 2026, 7:54 p.m.