Triple

T15590040
Position Surface form Disambiguated ID Type / Status
Subject Abington Social Library E374718 entity
Predicate locatedIn P40 FINISHED
Object Abington E161884 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: Abington | Statement: [Abington Social Library, locatedIn, Abington]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abington
Context triple: [Abington Social Library, locatedIn, Abington]
  • A. Abington chosen
    Abington is a small suburban town in Plymouth County, southeastern Massachusetts, known for its residential character and proximity to Boston.
  • B. Abington
    Abington is a small settlement in South Lanarkshire, Scotland, historically associated with the surrounding Clydesdale region.
  • C. Abington Township
    Abington Township is a suburban municipality in Montgomery County, Pennsylvania, known for its residential communities, public parks, and regional rail access to Philadelphia.
  • D. Oakboro
    Oakboro is a small town located in Stanly County in the U.S. state of North Carolina.
  • E. Newtowne
    Newtowne was the original 17th-century name for what later became the city of Cambridge, Massachusetts, a prominent early colonial settlement near Boston.
  • 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_69d85cce25008190b13b52745fbd719b completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e4b903c8190a35f9267cb38e721 completed April 16, 2026, 2:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff4c53617c8190b4367eee351dc025 completed May 9, 2026, 3:01 p.m.
Created at: April 10, 2026, 4:11 a.m.