Triple

T30970334
Position Surface form Disambiguated ID Type / Status
Subject MBTA Line 12 E789076 entity
Predicate publicBranding P11989 FINISHED
Object MBTA Commuter Rail Lowell Line NE NERFINISHED

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 Commuter Rail Lowell Line | Statement: [MBTA Line 12, publicBranding, MBTA Commuter Rail Lowell Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicBranding
Context triple: [MBTA Line 12, publicBranding, MBTA Commuter Rail Lowell Line]
  • A. exportBrand
    Indicates a relationship where a brand is sold or distributed outside its home market into foreign or international markets.
  • B. hasBranding chosen
    Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
  • C. brandingReplaced
    Indicates that one branding has been superseded or substituted by another branding.
  • D. sharesBrandingWith
    Indicates that two entities use the same or closely related branding elements, such as name, logo, or visual identity.
  • E. brandingNote
    Indicates that an entity has an associated note or comment specifically about its branding, such as style, usage, or presentation guidelines.
  • F. None of above.

Provenance (3 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_69f224c3a6b48190951add9b7b7f0271 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe59d11e9881909d2f33b7c717030e completed May 8, 2026, 9:46 p.m.
PD Predicate disambiguation batch_69fe394fdfbc8190a931926ae3635cbf completed May 8, 2026, 7:28 p.m.
Created at: April 29, 2026, 8:54 p.m.