Triple

T20732308
Position Surface form Disambiguated ID Type / Status
Subject Mid-Atlantic English E509600 entity
Predicate overlapsWith P1867 FINISHED
Object Baltimore English NE NERFINISHED

How this triple was built (3 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: Baltimore English | Statement: [Mid-Atlantic English, overlapsWith, Baltimore English]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baltimore English
Context triple: [Mid-Atlantic English, overlapsWith, Baltimore English]
  • A. Mid-Atlantic English
    Mid-Atlantic English is a regional variety of American English spoken in the coastal states between New England and the South, characterized by distinctive vowel patterns and lexical features found in areas such as New Jersey, Pennsylvania, and Delaware.
  • B. Boston English
    Boston English is a distinctive regional dialect of American English spoken in and around Boston, Massachusetts, known for features like non-rhotic pronunciation and unique local vocabulary.
  • C. New Jersey English
    New Jersey English is a regional variety of American English characterized by distinct phonological and lexical features that vary notably between its northern and southern areas.
  • D. Estuary English
    Estuary English is a variety of English spoken in and around London and the southeast of England, characterized by features that blend aspects of Received Pronunciation and regional accents such as Cockney.
  • E. Appalachian English
    Appalachian English is a distinctive regional dialect of American English spoken in the Appalachian Mountains, known for its unique pronunciation, vocabulary, and grammatical features.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Baltimore English
Target entity description: Baltimore English is a regional dialect of American English spoken in and around Baltimore, Maryland, characterized by distinctive vowel pronunciations and local vocabulary that align it with the broader Mid-Atlantic dialect region.
  • A. Mid-Atlantic English chosen
    Mid-Atlantic English is a regional variety of American English spoken in the coastal states between New England and the South, characterized by distinctive vowel patterns and lexical features found in areas such as New Jersey, Pennsylvania, and Delaware.
  • B. Boston English
    Boston English is a distinctive regional dialect of American English spoken in and around Boston, Massachusetts, known for features like non-rhotic pronunciation and unique local vocabulary.
  • C. New Jersey English
    New Jersey English is a regional variety of American English characterized by distinct phonological and lexical features that vary notably between its northern and southern areas.
  • D. Estuary English
    Estuary English is a variety of English spoken in and around London and the southeast of England, characterized by features that blend aspects of Received Pronunciation and regional accents such as Cockney.
  • E. Appalachian English
    Appalachian English is a distinctive regional dialect of American English spoken in the Appalachian Mountains, known for its unique pronunciation, vocabulary, and grammatical features.
  • F. None of above.

Provenance (2 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c1ee49a48190876fa05eb291e54e completed April 21, 2026, 12:16 a.m.
Created at: April 16, 2026, 12:31 p.m.