Triple
T17730769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolaj Boyle |
E442578
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Boyle |
—
|
NE NERFINISHED |
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: [Nikolaj Boyle, familyName, Boyle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boyle Context triple: [Nikolaj 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.
Boyle
Boyle is a small historic town in western Ireland known for landmarks like Boyle Abbey and its scenic setting near Lough Key in County Roscommon.
-
D.
Boyce
Boyce is an English surname borne by various notable individuals across fields such as music, politics, and literature.
-
E.
Colhoun
Colhoun is a Scottish surname, historically associated with Clan Colquhoun and its descendants.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e69f288190900027641952f198 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 10:08 a.m.