Triple
T3870224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutherford B. Hayes |
E91966
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Rutherford |
E91966
|
NE FINISHED |
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: Rutherford | Statement: [Rutherford B. Hayes, givenName, Rutherford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rutherford Context triple: [Rutherford B. Hayes, givenName, Rutherford]
-
A.
Rutherford
Rutherford is a residential and industrial suburb in the City of Maitland in New South Wales, Australia.
-
B.
Rutherford
chosen
Rutherford is the given name of Rutherford B. Hayes, the 19th president of the United States.
-
C.
Moseley
Moseley is a surname most notably associated with Jonny Moseley, the American Olympic gold medal–winning freestyle skier.
-
D.
Mancunium
Mancunium is the Latin name for the ancient Roman settlement that later developed into the modern city of Manchester in northwest England.
-
E.
Yates
Yates is a surname of English origin borne by various notable individuals across literature, politics, sports, and other fields.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec533828819080f52dae15fdbecd |
completed | March 9, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5124769c081909111b4bcac6baa78 |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.