Triple
T11363856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharman Macdonald |
E269152
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Sharman |
E416800
|
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: Sharman | Statement: [Sharman Macdonald, givenName, Sharman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sharman Context triple: [Sharman Macdonald, givenName, Sharman]
-
A.
Sharman
chosen
Sharman is a surname most notably associated with Helen Sharman, the first British astronaut and the first Western European woman in space.
-
B.
Shaiman
Shaiman is a surname most notably associated with Marc Shaiman, the American composer and lyricist known for his work in film, television, and musical theatre.
-
C.
Kashmore
Kashmore is a town in Pakistan’s Sindh province that serves as a regional hub near the Guddu Barrage on the Indus River.
-
D.
Shanly
Shanly is a small rural community located within the Township of South Dundas in eastern Ontario, Canada.
-
E.
Shon
Shon is a given name that functions as an alternative spelling of the more common name Shaun (or Sean).
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea4589908190948a8225768e1eec |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5565df5508190aeda7d064bceb157 |
completed | April 19, 2026, 10:25 p.m. |
Created at: April 8, 2026, 9:33 p.m.