Triple

T22007157
Position Surface form Disambiguated ID Type / Status
Subject Simpsonville E543476 entity
Predicate locatedNear P294 FINISHED
Object Mauldin NE NERFINISHED

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: Mauldin | Statement: [Simpsonville, locatedNear, Mauldin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mauldin
Context triple: [Simpsonville, locatedNear, Mauldin]
  • A. Mauldin
    Mauldin is the surname of American music producer, songwriter, and record executive Jermaine Dupri.
  • B. Mauldin chosen
    Mauldin is a city in South Carolina, United States, known as a suburban community within the Greenville metropolitan area.
  • C. Chesnee
    Chesnee is a small city in northern South Carolina known for its rural character and proximity to the Spartanburg–Gaffney area.
  • D. Saylesville
    Saylesville is a historic mill village located within the town of Lincoln in Providence County, Rhode Island.
  • E. Wilmore
    Wilmore is a small city in central Kentucky known for its strong Christian academic community and as the home of Asbury University and Asbury Theological Seminary.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e2db934819095556760c7d85e4d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127a18c1081909d15aa7ed4b725e3 completed April 28, 2026, 9:33 p.m.
Created at: April 16, 2026, 8:21 p.m.