Triple

T8000746
Position Surface form Disambiguated ID Type / Status
Subject Barnwell parish E186241 entity
Predicate hasPart P35 FINISHED
Object Barnwell E487324 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: Barnwell | Statement: [Barnwell parish, hasPart, Barnwell]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Barnwell
Context triple: [Barnwell parish, hasPart, Barnwell]
  • A. Barnwell chosen
    Barnwell is a surname of English origin borne by various notable individuals, including military figures such as Colonel John Barnwell.
  • B. Summerville
    Summerville is a small city in Chattooga County in northwestern Georgia, known as the county seat and a local hub for the surrounding rural area.
  • C. Horry
    Horry is a diminutive or nickname commonly used as a short form of the given name Horace.
  • D. Pickens, South Carolina
    Pickens, South Carolina is a small city in the northwestern part of the state, located in the foothills of the Blue Ridge Mountains.
  • E. Moncks Corner
    Moncks Corner is a small town in South Carolina known as a historic community near Charleston and the Santee Cooper lakes.
  • 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_69ca82aaaf24819084b94d18f699ba53 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c9cd06081908b62bb41e228c321 completed March 31, 2026, 3:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe11aefc88190bcf614e936455927 completed March 31, 2026, 2:58 p.m.
Created at: March 30, 2026, 5:17 p.m.