Triple
T18655581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheffield Frazier |
E456055
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Sheffield Frazier |
—
|
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: Sheffield Frazier | Statement: [Sheffield Frazier, hasName, Sheffield Frazier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sheffield Frazier Context triple: [Sheffield Frazier, hasName, Sheffield Frazier]
-
A.
Sheffield Frazier
chosen
Sheffield Frazier is a person notable enough to be recognized as a namesake or distinguished bearer of the surname Frazier.
-
B.
Frick
Frick is a surname most prominently associated with American industrialist and art patron Henry Clay Frick.
-
C.
Frick
Frick is a municipality in the canton of Aargau in northern Switzerland, known for its location on major rail and road routes between Basel and Zurich.
-
D.
Frazier
Frazier is a common English-language surname of Scottish and Irish origin, borne by various notable figures in sports, entertainment, and public life.
-
E.
Richmond Weir
Richmond Weir is a river control structure on the River Thames in southwest London that helps regulate water levels as part of the Richmond Lock and Weir complex.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55084012881909b9dd60565011c86 |
completed | April 19, 2026, 10 p.m. |
Created at: April 10, 2026, 11:47 a.m.