Triple

T33567441
Position Surface form Disambiguated ID Type / Status
Subject Princeton Township E859794 entity
Predicate sharedServicesWith P135898 FINISHED
Object Borough of Princeton 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: Borough of Princeton | Statement: [Princeton Township, sharedServicesWith, Borough of Princeton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sharedServicesWith
Context triple: [Princeton Township, sharedServicesWith, Borough of Princeton]
  • A. sharesServicesWith
    Indicates that two entities make use of, provide, or are connected through the same services or service infrastructure.
  • B. hasSharedServices chosen
    Indicates that two or more entities use or are supported by the same underlying services, resources, or service infrastructure.
  • C. servicePatternSharedWith
    Indicates that two or more entities use or follow the same service pattern, such as an identical sequence, schedule, or configuration of service delivery.
  • D. providesServicesJointlyWith
    Indicates that two or more entities collaborate to offer services together as a joint provision rather than independently.
  • E. sharesRitesWith
    Indicates that two entities participate in or observe the same religious, ceremonial, or ritual practices.
  • 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_69f3497c1d288190a844ea699914e038 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ffada24d188190a576a02dc280a7fb completed May 9, 2026, 9:56 p.m.
PD Predicate disambiguation batch_69ffad46d6ac819081772f408b1389d5 completed May 9, 2026, 9:55 p.m.
Created at: May 1, 2026, 1:40 a.m.