Triple

T12972051
Position Surface form Disambiguated ID Type / Status
Subject Deal, New Jersey E321421 entity
Predicate locatedInCountySeat P40853 FINISHED
Object not a county seat 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: not a county seat | Statement: [Deal, New Jersey, locatedInCountySeat, not a county seat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInCountySeat
Context triple: [Deal, New Jersey, locatedInCountySeat, not a county seat]
  • A. isInCountySeatOf
    Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
  • B. isInCountySeat chosen
    Indicates that one entity (typically a place or facility) is located within the county seat of a given county.
  • C. hasCountySeatWithin
    Indicates that the designated county’s official administrative center (county seat) is located within the specified geographic area or boundary.
  • D. containsCountySeat
    Indicates that one administrative region or area includes within its boundaries the designated county seat location of a county.
  • E. isInCountySeatCity
    Indicates that a given location or entity is situated within the city that serves as the county seat (administrative center) of a county.
  • 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_69d80763bd6c819094437da5b20b01d2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97f2a71a0819098bb6cf8a4b2208a completed April 10, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69d97dbdd94c8190ac4bbecca02dc77b completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 8:36 p.m.