Triple

T892110
Position Surface form Disambiguated ID Type / Status
Subject Barra E19261 entity
Predicate hasVariant P455 FINISHED
Object Barre E73526 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: Barre | Statement: [Barra, hasVariant, Barre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barre
Context triple: [Barra, hasVariant, Barre]
  • A. Barre, Vermont chosen
    Barre, Vermont is a small city in central Vermont known historically for its granite quarries and stonecutting industry.
  • B. Burlington
    Burlington is a suburban town in Massachusetts known for its proximity to Boston and its mix of residential neighborhoods, office parks, and retail centers.
  • C. Burlington
    Burlington is a historic city in present-day New Jersey that once served as the colonial capital of the Province of New Jersey.
  • D. Lenox
    Lenox is a small, historic town in western Massachusetts known for its cultural attractions, including Tanglewood, the summer home of the Boston Symphony Orchestra.
  • E. Paris, Maine
    Paris, Maine is a small town in western Maine that serves as the administrative and commercial center of Oxford County.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad0304b081908d4c92bb2beadb81 completed March 1, 2026, 9:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3b9b7eb88190b7fa4f9dbcc73d64 completed March 7, 2026, 2:52 p.m.
Created at: March 1, 2026, 7:39 p.m.