Triple

T26844118
Position Surface form Disambiguated ID Type / Status
Subject New Jersey Transit River Line E675866 entity
Predicate servesCity P82 FINISHED
Object Riverside, New Jersey
Riverside, New Jersey is a small township in Burlington County along the Delaware River, historically known for its industrial roots and commuter access to nearby Philadelphia.
E2290798 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: Riverside, New Jersey | Statement: [New Jersey Transit River Line, servesCity, Riverside, 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: Riverside, New Jersey
Triple: [New Jersey Transit River Line, servesCity, Riverside, New Jersey]
Generated description
Riverside, New Jersey is a small township in Burlington County along the Delaware River, historically known for its industrial roots and commuter access to nearby 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_69eee9b8d5e88190a07d3455c0fbb21f completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61b4bb4f88190acd826f0fb9b7c3b completed May 2, 2026, 3:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5c00f973808190ada8b72ed6d7dedb completed July 18, 2026, 10:40 p.m.
NEDg Description generation batch_6a5c0184266481908fb79e82f41324f5 completed July 18, 2026, 10:43 p.m.
NED2 Entity disambiguation (via description) batch_6a5c02133a80819099656f6ee7ada8ae completed July 18, 2026, 10:45 p.m.
Created at: April 27, 2026, 5:09 a.m.