Triple

T763720
Position Surface form Disambiguated ID Type / Status
Subject A92 road E16127 entity
Predicate connects P390 FINISHED
Object Montrose E27714 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: Montrose | Statement: [A92 road, connects, Montrose]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Montrose
Context triple: [A92 road, connects, Montrose]
  • A. Montrose chosen
    Montrose is a coastal town in eastern Scotland known for its historic harbor, sandy beach, and surrounding nature reserves.
  • B. Toa Alta
    Toa Alta is a municipality in northern Puerto Rico known for its suburban communities and integration into the greater San Juan metropolitan region.
  • C. Colma
    Colma is a small town in San Mateo County, California, best known for its numerous cemeteries and nickname as the "City of Souls."
  • D. Livingston
    Livingston is a large post-war new town in West Lothian, Scotland, known as a major residential and commercial centre within the Edinburgh commuter belt.
  • E. Livingston
    Livingston is a prominent American family name historically associated with influential political figures, landowners, and statesmen, particularly in New York.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a493684ee48190bd43b7c78da4aec8 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a69c8c448190a036a04fd8fdd2c2 completed March 1, 2026, 8:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7c009d5048190b2a137b6ed8b60ec completed March 4, 2026, 5:15 a.m.
Created at: March 1, 2026, 7:37 p.m.