Triple
T16688905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davie County, North Carolina |
E405540
|
entity |
| Predicate | largestCity |
P235
|
FINISHED |
| Object | Mocksville |
E1034994
|
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: Mocksville | Statement: [Davie County, North Carolina, largestCity, Mocksville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mocksville Context triple: [Davie County, North Carolina, largestCity, Mocksville]
-
A.
Mocksville
chosen
Mocksville is a small town in North Carolina that serves as the county seat and administrative center of Davie County.
-
B.
Smithville
Smithville is a small unincorporated community and historic village located within Galloway Township in Atlantic County, New Jersey.
-
C.
Smithville
Smithville is the former historic name of the present-day Town of Loomis in Placer County, California.
-
D.
Maynardville
Maynardville is a small city in Union County, Tennessee, known as the county seat and part of the greater Knoxville metropolitan region.
-
E.
Youngsville
Youngsville is a small town in Franklin County, North Carolina, located just north of the Raleigh–Durham metropolitan area.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea80d88819091fc61ed3c01955a |
completed | April 18, 2026, 12:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0091966fbc81908cd1db230ddbb82b |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.