Triple

T37410130
Position Surface form Disambiguated ID Type / Status
Subject Franklin Township, Gloucester County, New Jersey E929540 entity
Predicate contains P35 FINISHED
Object Porchtown, New Jersey
Porchtown, New Jersey is a small unincorporated community located within Franklin Township in Gloucester County.
E2296731 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: Porchtown, New Jersey | Statement: [Franklin Township, Gloucester County, New Jersey, contains, Porchtown, 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: Porchtown, New Jersey
Triple: [Franklin Township, Gloucester County, New Jersey, contains, Porchtown, New Jersey]
Generated description
Porchtown, New Jersey is a small unincorporated community located within Franklin Township in Gloucester 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_69f76ebde49481908566cd96b37ccc84 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8d839a4881908db8726ecbc3cfac completed May 6, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a82aa4929a88190a127e3dda1b4aba5 completed Aug. 17, 2026, 6:29 a.m.
NEDg Description generation batch_6a82aaac39a88190b86f957092368c86 completed Aug. 17, 2026, 6:31 a.m.
NED2 Entity disambiguation (via description) batch_6a82ab07c1848190b2afc4c5e23b116c completed Aug. 17, 2026, 6:32 a.m.
Created at: May 3, 2026, 4:16 p.m.