Triple
T7703733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Boyce |
E174561
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | William Boyce |
E174561
|
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: William Boyce | Statement: [William Boyce, name, William Boyce]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: William Boyce Context triple: [William Boyce, name, William Boyce]
-
A.
William Boyce
chosen
William Boyce was an 18th-century English composer and organist best known for his church music, symphonies, and the influential collection "Cathedral Music."
-
B.
George Lloyd
George Lloyd was an American character actor active in the mid-20th century, appearing in numerous films and serials, often in supporting or bit roles.
-
C.
Charles Jennens
Charles Jennens was an 18th-century English librettist and patron best known for compiling the biblical text for Handel’s oratorio "Messiah."
-
D.
Samuel Burney
Samuel Burney was a 19th-century settler in Northern California after whom the scenic Burney Falls in Shasta County is named.
-
E.
John Bevan
John Bevan was a British intelligence officer who played a key role in planning and overseeing Allied deception operations during World War II.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7028bcb2c8190baa4e4b14abe2cc5 |
completed | March 27, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8acbc2024819083576f5a11c1e3a8 |
completed | March 29, 2026, 4:38 a.m. |
Created at: March 27, 2026, 4:03 p.m.