Triple

T2354673
Position Surface form Disambiguated ID Type / Status
Subject Leicester E47527 entity
Predicate isMulticulturalCity P38709 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: [Leicester, isMulticulturalCity, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMulticulturalCity
Context triple: [Leicester, isMulticulturalCity, true]
  • A. hasDistinctCulturalHeritage
    Indicates that an entity possesses a unique cultural background, traditions, or practices that distinguish it from other entities.
  • B. isGlobalCity
    Indicates that a city holds significant worldwide influence in areas such as economics, culture, politics, or connectivity, making it an important node in the global system.
  • C. countryOfCulturalSignificance
    Indicates that a country holds notable cultural importance or influence for a given entity, such as a person, group, object, or practice.
  • D. hasCulturalCommunity
    Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
  • E. isGlobalCityFor
    Indicates that a city holds significant global importance or influence for a specified country, region, or domain (e.g., economy, culture, or politics).
  • 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_69a88a1b678c8190bce986922ba60ce0 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abcb802da08190980100444010f91e completed March 7, 2026, 6:53 a.m.
PD Predicate disambiguation batch_69abc5981ce48190a3f7852d28276e11 completed March 7, 2026, 6:28 a.m.
PDg Predicate description generation batch_69abcb7ebb708190ba7edffee3c45d8b completed March 7, 2026, 6:53 a.m.
Created at: March 4, 2026, 7:54 p.m.