Triple
T2371296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timothy P. Boyle |
E46095
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Boyle |
E111086
|
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: Boyle | Statement: [Timothy P. Boyle, familyName, Boyle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boyle Context triple: [Timothy P. Boyle, familyName, Boyle]
-
A.
Boyle
chosen
Boyle is a surname of Irish origin most famously associated with the 17th-century natural philosopher and chemist Robert Boyle, a pioneer of modern experimental science.
-
B.
Boyle
Boyle is the vehicle registration prefix code used on license plates issued in Boyle County, Kentucky.
-
C.
Davy
Davy is a familiar diminutive form of the given name David, often used as a casual or affectionate nickname.
-
D.
Barlow
Barlow is a surname most notably associated with John Perry Barlow, the American poet, essayist, and co-founder of the Electronic Frontier Foundation.
-
E.
Briggs
Briggs is a surname most prominently associated with Lance Briggs, a former NFL linebacker best known for his career with the Chicago Bears.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc771302481908540e31abb5aeeba |
completed | March 7, 2026, 6:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aea8a2b1448190b19179cf379993ee |
completed | March 9, 2026, 11:01 a.m. |
Created at: March 4, 2026, 7:56 p.m.