Triple
T12049616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebekkah Brunson |
E286880
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Brunson |
E826243
|
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: Brunson | Statement: [Rebekkah Brunson, familyName, Brunson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brunson Context triple: [Rebekkah Brunson, familyName, Brunson]
-
A.
Brunson
chosen
Brunson is a surname most prominently associated in sports with NBA All-Star point guard Jalen Brunson.
-
B.
Lamon
Lamon is an archaeological site notable for inscriptions in the ancient Venetic language.
-
C.
Briscoe
Briscoe is a surname most notably associated with Dolph Briscoe, a prominent American rancher and politician who served as governor of Texas.
-
D.
Rennie
Rennie is a Scottish surname most notably associated with the family of civil engineers, including John Rennie the Younger.
-
E.
Bonderman
Bonderman is a surname most prominently associated with American billionaire investor and private equity pioneer David Bonderman.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d904227958819084dbd5eb2566c735 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49dd140a48190844f64c228e6367a |
completed | May 1, 2026, 12:34 p.m. |
Created at: April 8, 2026, 9:47 p.m.