Triple
T31535924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoxton Square practice, London |
E804599
|
entity |
| Predicate | notablePhysician |
P26156
|
FINISHED |
| Object | James Parkinson |
E229733
|
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: James Parkinson | Statement: [Hoxton Square practice, London, notablePhysician, James Parkinson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePhysician Context triple: [Hoxton Square practice, London, notablePhysician, James Parkinson]
-
A.
notablePractitioner
chosen
Indicates that an entity is a well-known or distinguished practitioner of a particular field, discipline, or activity.
-
B.
notableScientist
Indicates that the subject is a scientist who is widely recognized for significant contributions or impact in their field.
-
C.
notableProfessor
Indicates that a person holds or has held a professorship that is distinguished, prominent, or otherwise recognized as notable.
-
D.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
-
E.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
- F. None of above.
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b562e557c819089e812c8982129c4 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:03 p.m.