Triple
T16661383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UKF22 |
E404866
|
entity |
| Predicate | adminTerritoryType |
P92063
|
FINISHED |
| Object | ceremonial county |
—
|
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: ceremonial county | Statement: [UKF22, adminTerritoryType, ceremonial county]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminTerritoryType Context triple: [UKF22, adminTerritoryType, ceremonial county]
-
A.
adminTerritory
Indicates that one entity serves as the administrative authority or governing jurisdiction over a specified territory.
-
B.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
D.
administrativeTerritoryType
chosen
Indicates the classification of an administrative area according to its level or type of territorial governance (e.g., city, county, province).
-
E.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfee5448190bb44c4dadba5dcbd |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.