Triple

T13803383
Position Surface form Disambiguated ID Type / Status
Subject Rutland City E331696 entity
Predicate namedAfter P63 FINISHED
Object Rutland E64919 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: Rutland | Statement: [Rutland City, namedAfter, Rutland]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rutland
Context triple: [Rutland City, namedAfter, Rutland]
  • A. Rutland
    Rutland is an unincorporated community located in Bibb County, Georgia, United States.
  • B. Rutland
    Rutland is a small town in Worcester County, Massachusetts, known for its rural character and location near the geographic center of the state.
  • C. Rutland
    Rutland is a small historic county in the East Midlands of England, known for its rural character and Rutland Water reservoir.
  • D. Rutland chosen
    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.
  • E. Berkshire
    Berkshire is a historic county in South East England known for its royal connections, including Windsor Castle, and its mix of affluent towns and rural landscapes.
  • 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_69d81c59f8808190a851bc56afdc55e9 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de026c36108190a7436034a730a261 completed April 14, 2026, 9:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c70261c8819099408952f137456d completed May 3, 2026, 10:06 p.m.
Created at: April 9, 2026, 10:12 p.m.