Triple
T32466620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton & Hove City Council |
E829726
|
entity |
| Predicate | cameIntoEffectAsUnitaryAuthorityOn |
P49152
|
FINISHED |
| Object | 1 April 1997 |
—
|
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: 1 April 1997 | Statement: [Brighton & Hove City Council, cameIntoEffectAsUnitaryAuthorityOn, 1 April 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoEffectAsUnitaryAuthorityOn Context triple: [Brighton & Hove City Council, cameIntoEffectAsUnitaryAuthorityOn, 1 April 1997]
-
A.
unitaryAuthoritySince
chosen
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
B.
establishedAsUnionTerritoryOn
Indicates the date or event on which a region was formally designated and constituted as a union territory.
-
C.
wasFirstOfficiallyProclaimedIn
Indicates the time or place at which something was first formally and officially announced or declared.
-
D.
establishedAsProvinceIn
Indicates that an entity was formally designated or created as a province in a specified year or time period.
-
E.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c35217548190a7a5df687aeac236 |
completed | May 3, 2026, 3:38 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:57 a.m.