Triple
T11232980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aberdeen City council area |
E265872
|
entity |
| Predicate | hasCouncilAreaCode |
P97969
|
FINISHED |
| Object | S12000033 |
—
|
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: S12000033 | Statement: [Aberdeen City council area, hasCouncilAreaCode, S12000033]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilAreaCode Context triple: [Aberdeen City council area, hasCouncilAreaCode, S12000033]
-
A.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
-
B.
hasCouncilAreaStatus
Indicates that an entity holds the official designation or status of being a council area within an administrative or governmental structure.
-
C.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
D.
hasCouncilAreaPart
Indicates that one council area includes another council area as a constituent part within its administrative or geographic boundaries.
-
E.
associatedWithCouncilArea
Indicates that an entity has a formal or contextual relationship with a specific council (administrative) area.
- 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_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. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.