Triple
T14754421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Grenada |
E346692
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | John Byron |
E669750
|
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: John Byron | Statement: [Battle of Grenada, commander, John Byron]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: John Byron Context triple: [Battle of Grenada, commander, John Byron]
-
A.
John Byron
chosen
John Byron was an 18th-century British Royal Navy officer and circumnavigator, nicknamed "Foul-Weather Jack" for his frequent encounters with storms at sea.
-
B.
Sir John Byron
Sir John Byron was an English nobleman and politician of the 16th century, notable as an ancestor of the poet Lord Byron and a prominent member of the Byron family of Nottinghamshire.
-
C.
Byron
Byron is a small city in central Georgia, United States, known for its historic downtown and location along major transportation routes near Macon.
-
D.
Byron
Byron is the given name of Byron King-Noel, the 12th Baron Wentworth and grandson of the poet Lord Byron.
-
E.
Byron
Byron is a masculine given name of Old English origin, commonly associated with the English Romantic poet Lord Byron.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb9c725881908004368772fa528d |
completed | May 8, 2026, 3:05 p.m. |
Created at: April 10, 2026, 1:30 a.m.