Triple

T32405745
Position Surface form Disambiguated ID Type / Status
Subject Green Line A branch E828072 entity
Predicate successorService P78 FINISHED
Object MBTA bus route 501
MBTA bus route 501 is an express bus line in the Boston area that provides rapid commuter service between Brighton/Allston and downtown Boston.
E2007442 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: MBTA bus route 501 | Statement: [Green Line A branch, successorService, MBTA bus route 501]
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: MBTA bus route 501
Triple: [Green Line A branch, successorService, MBTA bus route 501]
Generated description
MBTA bus route 501 is an express bus line in the Boston area that provides rapid commuter service between Brighton/Allston and downtown Boston.

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_69f34919342c8190a4c3bf35a90d4e58 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c247928481908f5aa369adfd2906 completed May 3, 2026, 3:34 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34666d1a74819091cd20ede77dbeca completed June 18, 2026, 9:43 p.m.
NEDg Description generation batch_6a346712d6408190897672c47396895f completed June 18, 2026, 9:45 p.m.
NED2 Entity disambiguation (via description) batch_6a3467d8a7c08190a8a3abb44e404478 completed June 18, 2026, 9:49 p.m.
Created at: May 1, 2026, 12:53 a.m.