Triple
T20886224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond (surname) |
E514286
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Richman |
—
|
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: Richman | Statement: [Richmond (surname), hasVariant, Richman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Richman Context triple: [Richmond (surname), hasVariant, Richman]
-
A.
Richman
chosen
Richman is a surname most notably associated with American actor Peter Mark Richman, known for his extensive work in film and television.
-
B.
Reiche
Reiche is a German surname most notably associated with Maria Reiche, the mathematician and archaeologist famed for her work on the Nazca Lines in Peru.
-
C.
Riche
Riche is a variant spelling of the given name and surname Ritchie, used in various English-speaking contexts.
-
D.
Richie Rich
Richie Rich is a long-running Harvey Comics series about an absurdly wealthy, kind-hearted boy whose lavish lifestyle and adventures have made him an iconic child character in American pop culture.
-
E.
Bogatēs
Bogatēs was a Persian military commander known for leading Achaemenid forces during the siege of the Greek city of Eion in the early 5th century BCE.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d058d4dc81908398f8c75e30dc77 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 12:46 p.m.