Triple

T38209020
Position Surface form Disambiguated ID Type / Status
Subject Humphrey Street, Swampscott E1009285 entity
Predicate hasName P744 FINISHED
Object Humphrey Street
Humphrey Street is a notable roadway in Swampscott, Massachusetts, serving as one of the town’s main thoroughfares through residential and coastal areas.
E2294292 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: Humphrey Street | Statement: [Humphrey Street, Swampscott, hasName, Humphrey Street]
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: Humphrey Street
Triple: [Humphrey Street, Swampscott, hasName, Humphrey Street]
Generated description
Humphrey Street is a notable roadway in Swampscott, Massachusetts, serving as one of the town’s main thoroughfares through residential and coastal areas.

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_69f76dc94fcc8190bd2f55e81f9d6527 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcb13354508190bd9cd1509b7c8b6f completed May 7, 2026, 3:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7bcc7eb26c8190804c209c3270abbb completed Aug. 12, 2026, 1:29 a.m.
NEDg Description generation batch_6a7bccd542c88190b11866feda2f0be6 completed Aug. 12, 2026, 1:31 a.m.
NED2 Entity disambiguation (via description) batch_6a7bcd22b2b88190a9563429081a7652 completed Aug. 12, 2026, 1:32 a.m.
Created at: May 3, 2026, 4:30 p.m.