Triple

T2134644
Position Surface form Disambiguated ID Type / Status
Subject Royal Borough of Greenwich E46620 entity
Predicate createdAsLondonBorough P35022 FINISHED
Object 1965 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: 1965 | Statement: [Royal Borough of Greenwich, createdAsLondonBorough, 1965]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: createdAsLondonBorough
Context triple: [Royal Borough of Greenwich, createdAsLondonBorough, 1965]
  • A. boroughOf
    Indicates that one place is a borough that is administratively or geographically part of another, typically larger, municipal entity.
  • B. shireDistrict
    Indicates that one administrative area is a shire district governing or encompassing another area.
  • C. containsMetropolitanBorough
    Indicates that an administrative area includes within its boundaries one or more metropolitan boroughs as subordinate units.
  • D. hasLondonAssemblyConstituency
    Indicates that an entity is associated with a specific London Assembly constituency as its designated electoral or administrative area.
  • E. 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.
  • 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_69a88a174ab48190a5db20c132e5dccf completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbba24004819091ffb9440e8615fa completed March 7, 2026, 5:46 a.m.
PD Predicate disambiguation batch_69abb7bf56e481909b0f497d238451cc completed March 7, 2026, 5:29 a.m.
PDg Predicate description generation batch_69abb860a51c8190b4ae3bb1cedc0fa0 completed March 7, 2026, 5:32 a.m.
Created at: March 4, 2026, 7:44 p.m.