Triple
T3879126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emil Newman |
E92577
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Newman |
E82513
|
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: Newman | Statement: [Emil Newman, familyName, Newman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Newman Context triple: [Emil Newman, familyName, Newman]
-
A.
Newman
Newman is a remote mining town in Western Australia known primarily for its large iron ore operations and role as a major hub in the Pilbara region.
-
B.
Newman
chosen
Newman is a common English surname borne by numerous notable figures across fields such as film, music, politics, and academia.
-
C.
William Newman
William Newman is a name shared by several notable individuals, including figures in fields such as computer science, acting, and academia.
-
D.
Paton
Paton is a surname and given name of Scottish origin, used by various notable individuals in fields such as sports, politics, and the arts.
-
E.
Wesley
Wesley is a masculine given name of English origin, traditionally used in English-speaking countries.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec7438808190b6c90fcb3000ebe9 |
completed | March 9, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51253da2081908689f06975fb4db1 |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.