Triple

T23452549
Position Surface form Disambiguated ID Type / Status
Subject Haddon Township, New Jersey E567822 entity
Predicate hasNeighborhood P40 FINISHED
Object Bettlewood, New Jersey
Bettlewood, New Jersey is a residential neighborhood within Haddon Township in Camden County, known for its suburban character and proximity to Philadelphia.
E1598778 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: Bettlewood, New Jersey | Statement: [Haddon Township, New Jersey, hasNeighborhood, Bettlewood, 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: Bettlewood, New Jersey
Triple: [Haddon Township, New Jersey, hasNeighborhood, Bettlewood, New Jersey]
Generated description
Bettlewood, New Jersey is a residential neighborhood within Haddon Township in Camden County, known for its suburban character and proximity to Philadelphia.

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_69e2458b4c888190b1d7998f9862a558 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a64ded5c8190bd50ac5b9bbb0f5f completed April 29, 2026, 6:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f53792d5c8190a3cb6c76c67aca3d completed May 21, 2026, 6:48 p.m.
NEDg Description generation batch_6a0f5537b2c081909bf3e35e1a1a6460 completed May 21, 2026, 6:55 p.m.
NED2 Entity disambiguation (via description) batch_6a0f55e0952c81908bd1b676db89f1b2 completed May 21, 2026, 6:58 p.m.
Created at: April 17, 2026, 5:52 p.m.