Triple

T22976404
Position Surface form Disambiguated ID Type / Status
Subject United States Census Bureau Jefferson County division E571330 entity
Predicate boundaryMatches P77197 FINISHED
Object Jefferson County, Kentucky administrative boundary 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: Jefferson County, Kentucky administrative boundary | Statement: [United States Census Bureau Jefferson County division, boundaryMatches, Jefferson County, Kentucky administrative boundary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boundaryMatches
Context triple: [United States Census Bureau Jefferson County division, boundaryMatches, Jefferson County, Kentucky administrative boundary]
  • A. boundaryIdentifiedWith chosen
    Indicates that the boundary of one entity is treated as equivalent to, or merged with, the boundary of another entity.
  • B. boundaryExpression
    Indicates a limiting or constraining condition that defines the allowable range, scope, or behavior of something within a system or context.
  • C. boundaryBetween
    Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
  • D. borderStraddling
    Indicates that something (such as a feature, structure, or area) extends across and occupies territory on both sides of a border between two regions or jurisdictions.
  • E. boundaryCase
    Indicates that one entity represents a limiting or extreme condition used to test or define the valid range or behavior of another entity.
  • 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_69e245b3c50481908bb3741ec9f40862 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f182369b548190a6630655a6e0bb39 completed April 29, 2026, 3:59 a.m.
PD Predicate disambiguation batch_69ef3b9101f48190a06c69dff26c6441 completed April 27, 2026, 10:33 a.m.
Created at: April 17, 2026, 3:48 p.m.