Triple
T14904464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C. R. Ashbee |
E360091
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ashbee |
E360091
|
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: Ashbee | Statement: [C. R. Ashbee, familyName, Ashbee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashbee Context triple: [C. R. Ashbee, familyName, Ashbee]
-
A.
Ashbee
chosen
Ashbee is an English surname most notably associated with C. R. Ashbee, a prominent designer and key figure in the Arts and Crafts movement.
-
B.
Beazley
Beazley is an English-language surname most prominently associated with Australian politician Kim Beazley and his family.
-
C.
Shadbolt
Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
-
D.
Beeton
Beeton is the surname most famously associated with Mrs. Isabella Beeton, the 19th-century English author of the influential household management and cookery book "Mrs Beeton's Book of Household Management."
-
E.
Raywick
Raywick is a small rural city in Marion County, Kentucky, known for its tight-knit community and location amid the rolling hills of central Kentucky.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded60cd5588190b1efecc2b220da69 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72b4e4f88190af7e859d93dbbd28 |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:12 a.m.