Triple

T37201531
Position Surface form Disambiguated ID Type / Status
Subject Borough Council of Carlstadt E922049 entity
Predicate hasJurisdiction P285 FINISHED
Object Borough of Carlstadt
The Borough of Carlstadt is a small municipal community in Bergen County, New Jersey, governed locally by a borough council and mayor.
E470588 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: Borough of Carlstadt | Statement: [Borough Council of Carlstadt, hasJurisdiction, Borough of Carlstadt]
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: Borough of Carlstadt
Triple: [Borough Council of Carlstadt, hasJurisdiction, Borough of Carlstadt]
Generated description
The Borough of Carlstadt is a small municipal community in Bergen County, New Jersey, governed locally by a borough council and mayor.

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_69f76ea4849481909b4a3073efb0114c completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb36453030819092164ede66da2d36 completed May 6, 2026, 12:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40361d77108190b780b0486ccf80d3 completed June 27, 2026, 8:44 p.m.
NEDg Description generation batch_6a403692b8c0819080608b791a585931 completed June 27, 2026, 8:46 p.m.
NED2 Entity disambiguation (via description) batch_6a4037016aa881909a72d303ebec4756 completed June 27, 2026, 8:48 p.m.
Created at: May 3, 2026, 4:15 p.m.