Triple
T9647999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenville Drive |
E233255
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Greenville |
E698869
|
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: Greenville | Statement: [Greenville Drive, city, Greenville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Greenville Context triple: [Greenville Drive, city, Greenville]
-
A.
Greenville
Greenville is a residential neighborhood in the southern part of Jersey City, New Jersey, known for its diverse community and urban character.
-
B.
Greenville
Greenville is a village and census-designated place in the town of Smithfield in Providence County, Rhode Island, known for its suburban character and historic New England charm.
-
C.
Greenville
Greenville is a small New England town in southern New Hampshire known for its historic mill village character and riverside setting.
-
D.
Greenville
Greenville is a suburban community within the greater Dallas metropolitan area in Texas.
-
E.
Greenville
chosen
Greenville is a mid-sized city in the northwestern part of South Carolina known for its revitalized downtown, cultural amenities, and role as an economic hub in the Upstate region.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bac55b48190ab2a8f9bb83c951e |
completed | April 1, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc3b3d1c819092210b334da3e0d3 |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:13 p.m.