Triple
T20609758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reeth |
E506415
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | RICHMOND |
—
|
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: RICHMOND | Statement: [Reeth, postTown, RICHMOND]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RICHMOND Context triple: [Reeth, postTown, RICHMOND]
-
A.
RICHMOND
chosen
RICHMOND is a historic market town in North Yorkshire, England, known for its Norman castle, Georgian architecture, and picturesque setting on the River Swale.
-
B.
Richmond
Richmond is an Australian federal electoral division in northern New South Wales that includes coastal communities such as Tweed Heads and Byron Bay.
-
C.
Richmond
Richmond is a small settlement located in St. Mary Parish on the northern coast of Jamaica.
-
D.
Richmond
Richmond is a residential neighborhood in Halifax, Nova Scotia, historically associated with the Halifax Explosion and now located near Fort Needham Memorial Park.
-
E.
Richmond
Richmond is a small city in northern Utah known for its agricultural roots and proximity to Logan in Cache County.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad5e53c8190b0add34ce9b31d57 |
completed | April 20, 2026, 10:38 p.m. |
Created at: April 16, 2026, 11:41 a.m.