Triple

T29485858
Position Surface form Disambiguated ID Type / Status
Subject Ted (franchise) E747918 entity
Predicate setIn P1393 FINISHED
Object Boston
Boston is a historic and culturally significant city in the northeastern United States, known for its role in the American Revolution, prestigious universities, and distinctive New England character.
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: [Ted (franchise), setIn, 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: [Ted (franchise), setIn, Boston]
Generated description
Boston is a historic and culturally significant city in the northeastern United States, known for its role in the American Revolution, prestigious universities, and distinctive New England character.

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_69f0bd43ba30819095eb1cfc3adf525c completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66c05947c8190b34739a0a7c0201f completed May 2, 2026, 9:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a260c0e537c81909b6c6fa9e3a98662 completed June 8, 2026, 12:25 a.m.
NEDg Description generation batch_6a26109f203481909b329aa741b7ab40 completed June 8, 2026, 12:45 a.m.
NED2 Entity disambiguation (via description) batch_6a26145c30e08190b9910491cecc2e74 completed June 8, 2026, 1:01 a.m.
Created at: April 28, 2026, 4:08 p.m.