Triple
T14745271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elliott Nugent |
E346452
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Nugent |
E983418
|
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: Nugent | Statement: [Elliott Nugent, familyName, Nugent]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nugent Context triple: [Elliott Nugent, familyName, Nugent]
-
A.
Nugent
chosen
Nugent is a surname of Irish origin historically associated with Anglo-Norman nobility and borne by various notable figures in politics, the arts, and public life.
-
B.
Nouster
Nouster is a small settlement on the Orkney island of North Ronaldsay in Scotland.
-
C.
Ebersole
Ebersole is a surname most notably associated with American actress and singer Christine Ebersole.
-
D.
Tilghman
Tilghman is a masculine given name of English origin that has been borne by various notable American figures, including politicians and military officers.
-
E.
Guthry
Guthry is a variant spelling of the surname Guthrie, which is of Scottish origin.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d002708190a32a4a45e96fc389 |
completed | April 14, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb9638648190a2a3eb255ec5ae28 |
completed | May 8, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:30 a.m.