Triple

T33250479
Position Surface form Disambiguated ID Type / Status
Subject Frelinghuysen Township, New Jersey E851225 entity
Predicate contains P35 FINISHED
Object Marksboro, New Jersey
Marksboro, New Jersey is a small unincorporated community and historic village located within Frelinghuysen Township in Warren County.
E2292971 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: Marksboro, New Jersey | Statement: [Frelinghuysen Township, New Jersey, contains, Marksboro, 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: Marksboro, New Jersey
Triple: [Frelinghuysen Township, New Jersey, contains, Marksboro, New Jersey]
Generated description
Marksboro, New Jersey is a small unincorporated community and historic village located within Frelinghuysen Township in Warren County.

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_69f34963135c819084e7f1d483421f00 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6db215e208190aa9b307766440b9d completed May 3, 2026, 5:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7a4800a0ac8190955b765f8bedd0ea completed Aug. 10, 2026, 9:52 p.m.
NEDg Description generation batch_6a7a4888fc8c81909eb26ac31b26e35a completed Aug. 10, 2026, 9:54 p.m.
NED2 Entity disambiguation (via description) batch_6a7a4923561c8190b676b6333ccd4cab completed Aug. 10, 2026, 9:56 p.m.
Created at: May 1, 2026, 1:31 a.m.