Triple

T9140794
Position Surface form Disambiguated ID Type / Status
Subject Middlesbrough Council E219319 entity
Predicate wasEstablishedAsUnitaryAuthorityOn P49152 FINISHED
Object 1996 — 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: 1996 | Statement: [Middlesbrough Council, wasEstablishedAsUnitaryAuthorityOn, 1996]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasEstablishedAsUnitaryAuthorityOn
Context triple: [Middlesbrough Council, wasEstablishedAsUnitaryAuthorityOn, 1996]
  • A. unitaryAuthoritySince chosen
    Indicates the point in time from which an entity has held the status or role of a unitary authority.
  • B. isUnitaryAuthority
    Indicates that an entity functions as a single-tier local government body with full administrative authority over its area, without sharing powers with a higher or lower local authority.
  • C. existedAsAdministrativeCountyFrom
    Indicates that an entity functioned in the status of an administrative county starting from a specified point in time.
  • D. municipalityEstablished
    Indicates that a municipality was officially created or founded at a specific point in time.
  • E. partOfMunicipalitySince
    Indicates that an entity has been included within and administratively belonging to a specific municipality starting from a given point in 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_69ca83e012288190a5771058adbaabd2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cca8f2537881908956a9b0516e2d49 completed April 1, 2026, 5:11 a.m.
PD Predicate disambiguation batch_69cc6603ce8c8190bf6e8d6754bdec54 completed April 1, 2026, 12:25 a.m.
Created at: March 30, 2026, 7:19 p.m.