Triple
T4082604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond, Texas |
E87510
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Richmond, London |
E75879
|
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: Richmond, London | Statement: [Richmond, Texas, namedAfter, Richmond, London]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Richmond, London Context triple: [Richmond, Texas, namedAfter, Richmond, London]
-
A.
Richmond, Surrey, England
chosen
Richmond, Surrey, England is a historic town on the River Thames in southwest London, long associated with English royalty and aristocratic residences.
-
B.
City of London
The City of London is the historic and financial core of Greater London, renowned as one of the world’s leading global finance and business centers.
-
C.
Richmond upon Thames
Richmond upon Thames is a leafy, affluent borough in southwest London known for its riverside scenery, extensive parks like Richmond Park, and historic architecture along the River Thames.
-
D.
London, England
London, England is the capital and largest city of the United Kingdom, renowned as a global center for finance, culture, and politics.
-
E.
London
London is a major Ethereum network upgrade that introduced significant changes to the protocol’s fee market and transaction pricing mechanisms.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7933b481909bb3e02c6c04c8ee |
completed | March 9, 2026, 4:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562c6456081908cca823ebb13936a |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.