Triple

T33078729
Position Surface form Disambiguated ID Type / Status
Subject Belford, New Jersey E846443 entity
Predicate hasBodyOfWater P1778 FINISHED
Object Compton Creek
Compton Creek is a small waterway in Belford, New Jersey, that flows into Sandy Hook Bay and serves as part of the local coastal and tidal marsh ecosystem.
E2296371 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: Compton Creek | Statement: [Belford, New Jersey, hasBodyOfWater, Compton Creek]
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: Compton Creek
Triple: [Belford, New Jersey, hasBodyOfWater, Compton Creek]
Generated description
Compton Creek is a small waterway in Belford, New Jersey, that flows into Sandy Hook Bay and serves as part of the local coastal and tidal marsh ecosystem.

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_69f34954d46c8190a04a159cc5f99efd completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d3b48d508190a9eda28dd6e912fb completed May 3, 2026, 4:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a8268cacac08190983996eda0d19474 completed Aug. 17, 2026, 1:50 a.m.
NEDg Description generation batch_6a82692597ac8190b82bf11be71e9720 completed Aug. 17, 2026, 1:51 a.m.
NED2 Entity disambiguation (via description) batch_6a82695d2b9481908eb3bd233cd7893e completed Aug. 17, 2026, 1:52 a.m.
Created at: May 1, 2026, 1:25 a.m.