Triple

T24501733
Position Surface form Disambiguated ID Type / Status
Subject North Shore, Massachusetts E617949 entity
Predicate locatedNorthOf P305 FINISHED
Object Boston
Boston is the capital and largest city of Massachusetts, known for its pivotal role in American history, prestigious universities, and vibrant cultural and economic life.
E906091 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: Boston | Statement: [North Shore, Massachusetts, locatedNorthOf, Boston]
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: Boston
Triple: [North Shore, Massachusetts, locatedNorthOf, Boston]
Generated description
Boston is the capital and largest city of Massachusetts, known for its pivotal role in American history, prestigious universities, and vibrant cultural and economic life.

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_69e2d7f682108190a1a7ca5fd485ee8a completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2a80277748190b34b174e9ec528eb completed April 30, 2026, 12:53 a.m.
NED1 Entity disambiguation (via context triple) batch_6a101bce2da88190bd2128c1c997d6ac completed May 22, 2026, 9:03 a.m.
NEDg Description generation batch_6a102a1495b881909ece4b9968710976 completed May 22, 2026, 10:04 a.m.
NED2 Entity disambiguation (via description) batch_6a102ab86eb88190be992ea8d7008621 completed May 22, 2026, 10:06 a.m.
Created at: April 18, 2026, 2:23 a.m.