Triple

T14477566
Position Surface form Disambiguated ID Type / Status
Subject Cambridge E359011 entity
Predicate originalName P65 FINISHED
Object Newtowne E1101221 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: Newtowne | Statement: [Cambridge, originalName, Newtowne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newtowne
Context triple: [Cambridge, originalName, Newtowne]
  • A. Newtowne chosen
    Newtowne was the original 17th-century name for what later became the city of Cambridge, Massachusetts, a prominent early colonial settlement near Boston.
  • B. Trewoon
    Trewoon is a village in Cornwall, England, situated just outside the town of St Austell.
  • C. Abington
    Abington is a small suburban town in Plymouth County, southeastern Massachusetts, known for its residential character and proximity to Boston.
  • D. Abington
    Abington is a small settlement in South Lanarkshire, Scotland, historically associated with the surrounding Clydesdale region.
  • E. Lastoursville
    Lastoursville is a town in central Gabon known as a regional hub along the Trans-Gabon Railway and for its nearby cave systems and karst landscapes.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9248edb48190a74eb032aeaac027 completed April 14, 2026, 7:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6d8ccd608190afd23c903cd5686a completed May 8, 2026, 4:58 a.m.
Created at: April 10, 2026, 1:20 a.m.