Triple
T11699743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esther Sleepe Burney |
E278090
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Burney |
E941612
|
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: Burney | Statement: [Esther Sleepe Burney, familyName, Burney]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burney Context triple: [Esther Sleepe Burney, familyName, Burney]
-
A.
Burney
chosen
Burney is an English surname most notably associated with the 18th-century music historian and composer Charles Burney and his literary family.
-
B.
Brydges
Brydges is the surname of a prominent British aristocratic family that included James Brydges, 1st Duke of Chandos, a notable early 18th-century nobleman and patron of the arts.
-
C.
Burnes
Burnes is a surname that functions as a spelling variant of the more common family name Burns.
-
D.
Beynes
Beynes is a commune in the Yvelines department of the Île-de-France region in north-central France.
-
E.
Butterfielde
Butterfielde is a surname variant of Butterfield, typically of English origin.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47df68c81908a91919a69b4880d |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f0195739348190b40a378ca227cf85 |
completed | April 28, 2026, 2:20 a.m. |
Created at: April 8, 2026, 9:40 p.m.