Triple
T11232989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberdeen City council area |
E265872
|
entity |
| Predicate | hasCouncilWebsite |
P54690
|
FINISHED |
| Object | https://www.aberdeencity.gov.uk/ |
—
|
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: https://www.aberdeencity.gov.uk/ | Statement: [Aberdeen City council area, hasCouncilWebsite, https://www.aberdeencity.gov.uk/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilWebsite Context triple: [Aberdeen City council area, hasCouncilWebsite, https://www.aberdeencity.gov.uk/]
-
A.
hasLocalGovernmentWebsite
Indicates that an entity has an official website specifically for its local government or municipal administration.
-
B.
governingBodyWebsite
chosen
Indicates the official website associated with the governing body responsible for an entity.
-
C.
hasCouncilName
Indicates that an entity is associated with or identified by a specific council name.
-
D.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
E.
hasCouncilDistrict
Indicates that an entity is located within or represented by a specific council district.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.