Triple
T12355570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patten |
E294602
|
entity |
| Predicate | isRelatedSurname |
P3889
|
FINISHED |
| Object | Paton |
E294601
|
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: Paton | Statement: [Patten, isRelatedSurname, Paton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paton Context triple: [Patten, isRelatedSurname, Paton]
-
A.
Paton
chosen
Paton is a surname and given name of Scottish origin, used by various notable individuals in fields such as sports, politics, and the arts.
-
B.
Ewart
Ewart is a given name notably borne by the 19th-century British statesman William Ewart Gladstone.
-
C.
Poulson
Poulson is the codename for a later-generation Intel Itanium processor microarchitecture designed to improve performance and efficiency in enterprise and mission-critical servers.
-
D.
Bartley
Bartley is a surname most notably associated with American philosopher and scholar William W. Bartley.
-
E.
Pritchard
Pritchard is a Welsh-origin surname commonly found in English-speaking countries, derived from the patronymic "ap Richard" meaning "son of Richard."
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f8bc60c8190b0ceb84093e70db4 |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62ab4cdec8190849604ef2ec498ba |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:54 p.m.