Triple

T30862420
Position Surface form Disambiguated ID Type / Status
Subject Rumson E786095 entity
Predicate legislativeBody P239 FINISHED
Object Rumson Borough Council
Rumson Borough Council is the local governing body responsible for creating and overseeing municipal laws, policies, and budgets for the Borough of Rumson, New Jersey.
E1936525 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: Rumson Borough Council | Statement: [Rumson, legislativeBody, Rumson Borough Council]
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: Rumson Borough Council
Triple: [Rumson, legislativeBody, Rumson Borough Council]
Generated description
Rumson Borough Council is the local governing body responsible for creating and overseeing municipal laws, policies, and budgets for the Borough of Rumson, New Jersey.

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_69f224b91c14819084e764832fe67a57 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f691a92b6081909e009d05ee9023b2 completed May 3, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a28c7d44f248190be392500f35013ca completed June 10, 2026, 2:11 a.m.
NEDg Description generation batch_6a28d79e0f4c81908edfb7f88e6e0f04 completed June 10, 2026, 3:18 a.m.
NED2 Entity disambiguation (via description) batch_6a28d81535508190b99af1cc085f0883 completed June 10, 2026, 3:20 a.m.
Created at: April 29, 2026, 8:47 p.m.