Triple
T16219761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane Budden |
E393691
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Budden |
E1054615
|
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: Budden | Statement: [Jane Budden, hasFamilyName, Budden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Budden Context triple: [Jane Budden, hasFamilyName, Budden]
-
A.
Budden
chosen
Budden is the surname of Joe Budden, an American rapper, media personality, and host of "The Joe Budden Podcast."
-
B.
Burgin
Burgin is a small rural city in Mercer County, Kentucky, known for its tight-knit community and location near Herrington Lake.
-
C.
Dunston
Dunston is a suburban district on the south bank of the River Tyne in Gateshead, England, known historically for its riverside industry and later redevelopment.
-
D.
Dunston
Dunston is the mischievous orangutan from the family comedy film "Dunston Checks In," known for causing chaos in a luxury hotel.
-
E.
Bosseborn
Bosseborn is a village and district within the town of Höxter in North Rhine-Westphalia, Germany.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e227fabf708190a624c1ed8ce48b0a |
completed | April 17, 2026, 12:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0007987cd881908ebc01141028c0a5 |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:03 a.m.