Triple
T7247861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John Byron |
E156521
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Byron |
E646402
|
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: Byron | Statement: [Sir John Byron, familyName, Byron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Byron Context triple: [Sir John Byron, familyName, Byron]
-
A.
Byron
Byron is the middle name of American professional golfer Byron Nelson, one of the sport’s early 20th-century legends.
-
B.
Byron
Byron is a small city in central Georgia, United States, known for its historic downtown and location along major transportation routes near Macon.
-
C.
Byron
Byron is the given name of Byron King-Noel, the 12th Baron Wentworth and grandson of the poet Lord Byron.
-
D.
Byron
chosen
Byron is a masculine given name of Old English origin, commonly associated with the English Romantic poet Lord Byron.
-
E.
Byron
Byron is the given first name of Ban Johnson, the influential early 20th-century American baseball executive who served as the founding president of the American League.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea749fb08190841c0aa8c5bd0727 |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fa6ad54081908a0be2d1f7d6505e |
completed | March 28, 2026, 3:57 p.m. |
Created at: March 27, 2026, 2:56 p.m.