Triple
T5643395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenville County |
E124322
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Mauldin |
E248579
|
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: [Greenville County, contains, Mauldin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mauldin Context triple: [Greenville County, contains, Mauldin]
-
A.
Mauldin
chosen
Mauldin is a city in South Carolina, United States, known as a suburban community within the Greenville metropolitan area.
-
B.
Mauldin
Mauldin is the surname of American music producer, songwriter, and record executive Jermaine Dupri.
-
C.
Wilmore
Wilmore is an English-language surname borne by various notable individuals across fields such as entertainment, sports, and public service.
-
D.
Gordonton
Gordonton is a small rural settlement in the Waikato region of New Zealand, located near the city of Hamilton and known for its farming community and local heritage sites.
-
E.
Darbyville
Darbyville is the former name of the city now known as Macclenny in Baker County, Florida.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a7cd9c819087f86f60e8b65fc3 |
completed | March 22, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04d80396c81909e26da3b5ca5ea34 |
completed | March 22, 2026, 8:13 p.m. |
Created at: March 22, 2026, 3:41 p.m.