Triple
T14151661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Barnwell |
E350697
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Barnwell |
E487324
|
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: Barnwell | Statement: [Frank Barnwell, familyName, Barnwell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barnwell Context triple: [Frank Barnwell, familyName, Barnwell]
-
A.
Barnwell
chosen
Barnwell is a surname of English origin borne by various notable individuals, including military figures such as Colonel John Barnwell.
-
B.
Barnwell
Barnwell is a residential and historic area of Cambridge, England, located to the east of the city centre.
-
C.
Summerville
Summerville is a small city in Chattooga County in northwestern Georgia, known as the county seat and a local hub for the surrounding rural area.
-
D.
Horry
Horry is a diminutive or nickname commonly used as a short form of the given name Horace.
-
E.
Richburg, South Carolina
Richburg, South Carolina is a small town in Chester County known for its location along major transportation routes between Charlotte and Columbia.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6124e23481909e5132a40a1d8624 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd19395924819084d78815c3f12f43 |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 12:57 a.m.