Triple

T1323041
Position Surface form Disambiguated ID Type / Status
Subject Royal Victoria Place E28262 entity
Predicate locatedIn P40 FINISHED
Object Kent E5977 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: Kent | Statement: [Royal Victoria Place, locatedIn, Kent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kent
Context triple: [Royal Victoria Place, locatedIn, Kent]
  • A. Kent
    Kent is a suburban city in King County, Washington, known as a residential and industrial hub within the greater Seattle metropolitan area.
  • B. Kent chosen
    Kent is a county in southeastern England known for its historic towns, coastal landscapes, and nickname "the Garden of England."
  • C. Kent, England
    Kent, England is a historic county in southeastern England known for its coastal towns, rich agricultural land, and nickname "the Garden of England."
  • D. Yorkshire
    Yorkshire is a historic county in northern England known for its large size, distinctive cultural identity, and significant role in British political, industrial, and literary history.
  • E. Rutland
    Rutland is a small city in central Vermont known historically as a marble quarrying center and as a regional hub for commerce and outdoor recreation.
  • 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_69a498540a2481909e807a762280d3ba completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c19caa148190a1f5be734b7d9005 completed March 1, 2026, 10:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69acbf2e13dc8190902879be5fa69adb completed March 8, 2026, 12:13 a.m.
Created at: March 1, 2026, 7:55 p.m.