Triple
T844444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston upon Hull |
E18246
|
entity |
| Predicate | isUnitaryAuthority |
P20565
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kingston upon Hull, isUnitaryAuthority, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnitaryAuthority Context triple: [Kingston upon Hull, isUnitaryAuthority, true]
-
A.
isMetropolitanBorough
Indicates that an entity functions as a metropolitan borough, i.e., a local government district within a large urban area that has borough status.
-
B.
hasMetropolitanAuthorityOver
Indicates that one entity holds official governing or administrative authority over a metropolitan area or region associated with another entity.
-
C.
hasUnitaryAuthority
Indicates that one entity serves as the single, primary governing or administrative authority over another entity or area.
-
D.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
E.
localAuthorityArea
Indicates that one entity is a geographic or administrative area governed or managed by a specified local authority.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac09249c8190a8099b94a3c9e2cc |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.