Triple

T25091213
Position Surface form Disambiguated ID Type / Status
Subject Richmond Rural District E628460 entity
Predicate wasDistinctFrom P1612 FINISHED
Object Richmond municipal borough NE NERFINISHED

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: Richmond municipal borough | Statement: [Richmond Rural District, wasDistinctFrom, Richmond municipal borough]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasDistinctFrom
Context triple: [Richmond Rural District, wasDistinctFrom, Richmond municipal borough]
  • A. historicallyDistinctFrom
    Indicates that two entities are recognized as separate and not the same in historical context, despite any similarities or connections they may have.
  • B. isDistinctFrom chosen
    Indicates that two entities are not identical and can be clearly distinguished from one another.
  • C. chronologicallyDistinctFrom
    Indicates that two events or time-related entities occur at different, non-overlapping points in time.
  • D. differentiatedFrom
    Indicates that one entity is distinguished or set apart from another by identifying differences between them.
  • E. mechanicallyDistinctFrom
    Indicates that two entities differ in their mechanical properties, structure, or behavior such that they are not mechanically equivalent or interchangeable.
  • F. None of above.

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_69e2ff2f58e881908340527bc5d34f07 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f46d3f35848190b56a4373c97a7d64 completed May 1, 2026, 9:07 a.m.
PD Predicate disambiguation batch_69f4683472ec8190a483b3b8afe71720 completed May 1, 2026, 8:45 a.m.
Created at: April 18, 2026, 6:24 a.m.