Triple
T14545270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beazley |
E341275
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Beasley |
E130428
|
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: Beasley | Statement: [Beazley, hasSpellingVariant, Beasley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beasley Context triple: [Beazley, hasSpellingVariant, Beasley]
-
A.
Beasley
chosen
Beasley is a surname most prominently associated with DaMarcus Beasley, a former United States international soccer player known for his World Cup appearances and club career in MLS and Europe.
-
B.
Beals
Beals is a surname most prominently associated with American actress Jennifer Beals, known for her breakout role in the film "Flashdance."
-
C.
Beesley
Beesley is an English surname borne by various notable individuals, including actors and public figures.
-
D.
Beal
Beal is a surname most prominently associated with NBA All-Star shooting guard Bradley Beal.
-
E.
Bealings
Bealings is a small rural village and civil parish located in the English county of Suffolk.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bfc2b48190adb0897682c26a9a |
completed | April 14, 2026, 9:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a60f2f88190b08fdf0a3095d0a7 |
completed | May 8, 2026, 5:53 a.m. |
Created at: April 10, 2026, 1:22 a.m.