Triple

T1506327
Position Surface form Disambiguated ID Type / Status
Subject Kingston, Ontario E33909 entity
Predicate nickname P55 FINISHED
Object Limestone City E127859 NE 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: Limestone City | Statement: [Kingston, Ontario, nickname, Limestone City]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Limestone City
Context triple: [Kingston, Ontario, nickname, Limestone City]
  • A. Limestone City chosen
    Limestone City is a nickname for Kingston, Ontario, reflecting its many historic buildings constructed from local limestone.
  • B. Fountain City
    Fountain City is a suburban community and former unincorporated town now functioning as a neighborhood within the Knoxville metropolitan area in Tennessee.
  • C. Gate City
    Gate City is a commonly used nickname for Greensboro, North Carolina, reflecting its historic role as a major transportation and commercial hub.
  • D. River City
    River City is a popular nickname for Richmond, Virginia, highlighting the city's location along the James River and its historic riverfront character.
  • E. River City
    River City is a popular nickname for Sacramento, California, highlighting the city’s close connection to the nearby American and Sacramento Rivers.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a885f352a4819099b24ff15489dede completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a88735f8a8819089177a4d3e4a0211 completed March 4, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad2336cb4c81909df0cae469673dee completed March 8, 2026, 7:20 a.m.
Created at: March 4, 2026, 7:24 p.m.