Triple
T18397051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Redmond |
E449896
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Redmond |
—
|
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: Redmond | Statement: [John Redmond, familyName, Redmond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Redmond Context triple: [John Redmond, familyName, Redmond]
-
A.
Redmond
Redmond is a growing city in Deschutes County, Oregon, known as a regional hub for transportation, outdoor recreation, and access to Central Oregon’s high desert and Cascade Mountains.
-
B.
Redmond
chosen
Redmond is a surname of English origin borne by various notable individuals, including figures in entertainment and public life.
-
C.
City of Redmond
The City of Redmond is a municipal government in Washington State best known as the home of Microsoft and for its vibrant community events and parks.
-
D.
Renton
Renton is a suburban city in Washington State located just southeast of Seattle, known for its Boeing facilities and position at the south end of Lake Washington.
-
E.
Renton
Renton is a small town in West Dunbartonshire, Scotland, situated on the River Leven between Dumbarton and Alexandria.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5184777548190818365ee52ac88b7 |
completed | April 19, 2026, 6 p.m. |
Created at: April 10, 2026, 10:46 a.m.