Triple
T23036772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis Fry Richardson |
E573618
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Richardson |
—
|
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: Richardson | Statement: [Lewis Fry Richardson, familyName, Richardson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Richardson Context triple: [Lewis Fry Richardson, familyName, Richardson]
-
A.
Richardson
Richardson is a suburban city in the Dallas–Fort Worth metropolitan area known for its telecommunications industry and the University of Texas at Dallas.
-
B.
Richardson
chosen
Richardson is a common English-language surname borne by numerous notable individuals across fields such as politics, science, sports, and the arts.
-
C.
Lawrence
Lawrence is a city located within Marion County in the U.S. state of Indiana.
-
D.
Lawrence
Lawrence is a small historic gold-mining town in New Zealand’s Otago region.
-
E.
Lawrence
Lawrence is a common English surname of Norman origin, derived from the given name Laurence and historically associated with various notable families and individuals.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1850fe5348190b42259595d82cff4 |
completed | April 29, 2026, 4:12 a.m. |
Created at: April 17, 2026, 3:53 p.m.