Triple
T25976823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PA27 |
E645963
|
entity |
| Predicate | adminTerritoryLevel |
P87046
|
FINISHED |
| Object | council area of Argyll and Bute |
—
|
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: council area of Argyll and Bute | Statement: [PA27, adminTerritoryLevel, council area of Argyll and Bute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminTerritoryLevel Context triple: [PA27, adminTerritoryLevel, council area of Argyll and Bute]
-
A.
adminTerritory
Indicates that one entity serves as the administrative authority or governing jurisdiction over a specified territory.
-
B.
adminTerritoryName
Indicates the name assigned to an administrative territory within a larger governance or organizational structure.
-
C.
territorialLevel
Indicates the administrative or geographic tier at which something is defined, applied, or governed within a territorial hierarchy.
-
D.
sharesAdministrativeLevel
Indicates that two entities are associated with the same tier or rank within an administrative or governmental hierarchy.
-
E.
administrativeUnitLevel
chosen
Indicates the hierarchical level or rank of an administrative unit within an overall administrative or governmental structure.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 22, 2026, 8:52 a.m.