Triple

T17044983
Position Surface form Disambiguated ID Type / Status
Subject John H. Van Buskirk E413542 entity
Predicate possibleRegionOfResidence P62106 FINISHED
Object Hackensack, New Jersey 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: Hackensack, New Jersey | Statement: [John H. Van Buskirk, possibleRegionOfResidence, Hackensack, New Jersey]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: possibleRegionOfResidence
Context triple: [John H. Van Buskirk, possibleRegionOfResidence, Hackensack, New Jersey]
  • A. likelyResidence
    Indicates that an entity is probably located at, lives at, or is most commonly associated with a particular place of residence.
  • B. traditionalRegionOfResidence
    Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
  • C. intendedResidence
    Indicates that one entity is designated or planned to serve as the place where another entity will live or reside.
  • D. likelyRegion chosen
    Indicates that an entity is probably located in, associated with, or originates from a particular geographic region.
  • E. regionOfHabitation
    Indicates the geographic area or environment in which an entity typically lives or resides.
  • 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_69d886cd18288190b006abab23f811b7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3da9d7e988190a5e3991c7123f9b0 completed April 18, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69e35d60a588819084f53ef9f8b2e7c0 completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:33 a.m.