Triple

T17934599
Position Surface form Disambiguated ID Type / Status
Subject Old Tappan, New Jersey E448424 entity
Predicate adjacentTo P224 FINISHED
Object Northvale, New Jersey
Northvale, New Jersey is a small suburban borough in Bergen County known for its residential character and proximity to the New York state border.
E368760 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: Northvale, New Jersey | Statement: [Old Tappan, New Jersey, adjacentTo, Northvale, 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: Northvale, New Jersey
Triple: [Old Tappan, New Jersey, adjacentTo, Northvale, New Jersey]
Generated description
Northvale, New Jersey is a small suburban borough in Bergen County known for its residential character and proximity to the New York state border.

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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a5547b7881909dc41bb7dd34194f completed April 19, 2026, 9:50 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34a78132b08190ae997a74baffd39e completed June 19, 2026, 2:20 a.m.
NEDg Description generation batch_6a34a84e9e3881909614d79de44dd3cc completed June 19, 2026, 2:24 a.m.
NED2 Entity disambiguation (via description) batch_6a34a8dde9f48190b9912c18f2470edf completed June 19, 2026, 2:26 a.m.
Created at: April 10, 2026, 10:21 a.m.