Triple
T13321849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jermaine Dupri Mauldin |
E317333
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mauldin |
E317333
|
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: Mauldin | Statement: [Jermaine Dupri Mauldin, familyName, Mauldin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mauldin Context triple: [Jermaine Dupri Mauldin, familyName, Mauldin]
-
A.
Mauldin
chosen
Mauldin is the surname of American music producer, songwriter, and record executive Jermaine Dupri.
-
B.
Mauldin
Mauldin is a city in South Carolina, United States, known as a suburban community within the Greenville metropolitan area.
-
C.
Saylesville
Saylesville is a historic mill village located within the town of Lincoln in Providence County, Rhode Island.
-
D.
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.
-
E.
Wilmore
Wilmore is an English-language surname borne by various notable individuals across fields such as entertainment, sports, and public service.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9992ab83c8190982d9f54dff6919f |
completed | April 11, 2026, 12:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716efc3908190890e969c40694771 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:30 p.m.