Triple

T31335283
Position Surface form Disambiguated ID Type / Status
Subject Humarock, Massachusetts E799155 entity
Predicate adjacentTo P224 FINISHED
Object Rexhame, Massachusetts
Rexhame, Massachusetts is a coastal village in the town of Marshfield known for its Atlantic shoreline, residential beach community, and proximity to neighboring Humarock.
E1989043 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: Rexhame, Massachusetts | Statement: [Humarock, Massachusetts, adjacentTo, Rexhame, Massachusetts]
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: Rexhame, Massachusetts
Triple: [Humarock, Massachusetts, adjacentTo, Rexhame, Massachusetts]
Generated description
Rexhame, Massachusetts is a coastal village in the town of Marshfield known for its Atlantic shoreline, residential beach community, and proximity to neighboring Humarock.

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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69ee3cfb881908234c228855d154d completed May 3, 2026, 1:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2ed4c6527481908c8cb51248e892ee completed June 14, 2026, 4:20 p.m.
NEDg Description generation batch_6a2ed72d455881908a8f2cae86d5c859 completed June 14, 2026, 4:30 p.m.
NED2 Entity disambiguation (via description) batch_6a2ed7a8c33c8190b4e9d25ad5ab3446 completed June 14, 2026, 4:32 p.m.
Created at: April 29, 2026, 9:16 p.m.