Triple
T21564618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Peapo Bryson |
E532129
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bryson |
—
|
NE NERFINISHED |
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: Bryson | Statement: [Robert Peapo Bryson, familyName, Bryson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bryson Context triple: [Robert Peapo Bryson, familyName, Bryson]
-
A.
Bryson
chosen
Bryson is a masculine given name of English origin that has gained popularity in recent years.
-
B.
Bryan
Bryan is a mid-sized city in Central Texas known for its close association with neighboring College Station and Texas A&M University.
-
C.
Bryan
Bryan is a masculine given name of Celtic origin that is widely used in English-speaking countries.
-
D.
Bryse
Bryse is an alternative spelling of the given name Bryce, typically used as a modern or stylistic variant.
-
E.
Thaddeus Bryson
Thaddeus Bryson was a prominent local figure and early settler in western North Carolina whose influence and contributions to the area led to the nearby town being named in his honor.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e777c881908de84493fa939ff3 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 16, 2026, 6:30 p.m.