Triple
T18253340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Conyers |
E437156
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Conyers |
—
|
NE NERFINISHED |
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: Conyers | Statement: [John Conyers, familyName, Conyers]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Conyers Context triple: [John Conyers, familyName, Conyers]
-
A.
Conyers
Conyers is a small city in Rockdale County, Georgia, that functions as an outer suburb within the greater Atlanta metropolitan area.
-
B.
Guilford
Guilford is a town located within the Windham Region of Vermont, known for its rural character and New England landscape.
-
C.
Guilford
Guilford is a British territorial designation historically associated with the noble title of Baron Guilford.
-
D.
Rexford
Rexford is a masculine given name of English origin, historically borne by several notable American figures including economist and New Deal planner Rexford G. Tugwell.
-
E.
Pelham
chosen
Pelham is an English surname historically associated with prominent political and aristocratic families in Britain.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd82f81c81909ad4455954bd8caa |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 10:33 a.m.