Triple
T10223561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Trevor-Roper |
E242642
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hugh |
E20500
|
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: Hugh | Statement: [Hugh Trevor-Roper, givenName, Hugh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hugh Context triple: [Hugh Trevor-Roper, givenName, Hugh]
-
A.
Hugh
chosen
Hugh is a masculine given name of Germanic origin, commonly used in English-speaking countries.
-
B.
Henry
Henry is the given name of Henry A. Kissinger, the influential American diplomat and political scientist who served as U.S. Secretary of State and National Security Advisor.
-
C.
Henry
Henry is the given name of the influential American architect Henry Hobson Richardson, a key figure in 19th-century architecture.
-
D.
Henry
Henry is a common English surname borne by numerous notable individuals across politics, sports, and the arts.
-
E.
Henry
Henry is a masculine given name of Germanic origin that has been widely used by European royalty and notable historical figures.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa84a9ac819093d551005a1c8f3d |
completed | April 6, 2026, 12:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6a8457e9c819085f222bb002be892 |
completed | April 8, 2026, 7:11 p.m. |
Created at: April 6, 2026, 11:10 a.m.