Triple

T23628513
Position Surface form Disambiguated ID Type / Status
Subject Boston Opera Company E583539 entity
Predicate location P40 FINISHED
Object Boston
Boston is a historic New England city and the capital of Massachusetts, known for its pivotal role in the American Revolution, prestigious universities, and rich cultural institutions.
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 Opera Company, location, 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 Opera Company, location, Boston]
Generated description
Boston is a historic New England city and the capital of Massachusetts, known for its pivotal role in the American Revolution, prestigious universities, and rich cultural institutions.

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_69e248fc8d74819091bd5baef2f36f6f completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b1e5ae80819085c417e8d81b74ad completed April 29, 2026, 7:23 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f75e90bf0819094e30dca5ffced2b completed May 21, 2026, 9:15 p.m.
NEDg Description generation batch_6a0f767286c08190a694713418eac5a9 completed May 21, 2026, 9:17 p.m.
NED2 Entity disambiguation (via description) batch_6a0f77a3c6e4819080c8b07fc9dd5b62 completed May 21, 2026, 9:22 p.m.
Created at: April 17, 2026, 6:46 p.m.