Triple

T28255968
Position Surface form Disambiguated ID Type / Status
Subject Boston University women’s rowing team E712445 entity
Predicate homeCity P263 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 sports scenes.
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: [Boston University women’s rowing team, homeCity, 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: [Boston University women’s rowing team, homeCity, 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 sports scenes.

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_69efb5207eb08190827e4c34048030b1 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f643f4b1448190b5db963c0f041f9b completed May 2, 2026, 6:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15e694d3f481908182045934f42d90 completed May 26, 2026, 6:29 p.m.
NEDg Description generation batch_6a15eab3ba408190a06d71a8d71a8337 completed May 26, 2026, 6:47 p.m.
NED2 Entity disambiguation (via description) batch_6a15f326278481909dda2c686252aa23 completed May 26, 2026, 7:23 p.m.
Created at: April 27, 2026, 11:08 p.m.