Triple

T5754916
Position Surface form Disambiguated ID Type / Status
Subject Larksville, Pennsylvania E126941 entity
Predicate hasName P744 FINISHED
Object Larksville E481157 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: Larksville | Statement: [Larksville, Pennsylvania, hasName, Larksville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Larksville
Context triple: [Larksville, Pennsylvania, hasName, Larksville]
  • A. Larksville chosen
    Larksville is a small borough in northeastern Pennsylvania, United States, situated within the Wyoming Valley near the city of Wilkes-Barre.
  • B. Slatersville
    Slatersville is a historic village in North Smithfield, Rhode Island, known as one of America’s first planned mill villages centered around early textile manufacturing.
  • C. Yatesville
    Yatesville is a small town located in the U.S. state of Georgia.
  • D. Millerton
    Millerton is a small hamlet and village in Dutchess County, New York, known for its rural charm and proximity to the Taconic State Park and the Harlem Valley.
  • E. Stewarttown
    Stewarttown is a small community located within the town of Halton Hills in Ontario, Canada.
  • 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_69c00832aedc81909899801b141fa3b4 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02904dcf481909e4340a64ee1034e completed March 22, 2026, 5:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69c07e434aa88190b56e721c002d31b8 completed March 22, 2026, 11:41 p.m.
Created at: March 22, 2026, 3:49 p.m.