Triple
T16373702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emily McKay Beal |
E397626
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Beal |
E63389
|
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: Beal | Statement: [Emily McKay Beal, familyName, Beal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beal Context triple: [Emily McKay Beal, familyName, Beal]
-
A.
Beal
chosen
Beal is a surname most prominently associated with NBA All-Star shooting guard Bradley Beal.
-
B.
Related Beal
Related Beal is a Boston-based real estate development and investment firm known for major mixed-use, residential, and commercial projects in the Greater Boston area.
-
C.
Beale
Beale is a common English surname notably associated with various public figures and fictional characters, including the Beale family in the British soap opera "EastEnders."
-
D.
Bealings
Bealings is a small rural village and civil parish located in the English county of Suffolk.
-
E.
Beasley
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.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d559788190bd96c45ff0900fe6 |
completed | April 18, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003561f83481909223c99bb83ebdf4 |
completed | May 10, 2026, 7:36 a.m. |
Created at: April 10, 2026, 5:08 a.m.