Triple

T30479533
Position Surface form Disambiguated ID Type / Status
Subject Barrington, New Jersey E775540 entity
Predicate borderedBy P224 FINISHED
Object Tavistock, New Jersey
Tavistock, New Jersey is a tiny, affluent borough in Camden County best known for its private golf club and extremely small residential population.
E2292416 NE 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: Tavistock, New Jersey | Statement: [Barrington, New Jersey, borderedBy, Tavistock, New Jersey]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Tavistock, New Jersey
Triple: [Barrington, New Jersey, borderedBy, Tavistock, New Jersey]
Generated description
Tavistock, New Jersey is a tiny, affluent borough in Camden County best known for its private golf club and extremely small residential population.

Provenance (5 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_69f22497341481909c21ba329fadaa6b completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6871c7b4081908b43fb58b04f8c13 completed May 2, 2026, 11:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a6885a3140c819081db6c5f54f1c028 completed July 28, 2026, 10:34 a.m.
NEDg Description generation batch_6a68868437b88190be8282151e177e2f completed July 28, 2026, 10:37 a.m.
NED2 Entity disambiguation (via description) batch_6a688736bc0081909c07bb3eb0e4bb5a completed July 28, 2026, 10:40 a.m.
Created at: April 29, 2026, 8:12 p.m.