Triple
T11554086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Byng |
E273968
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Byng |
E228229
|
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: Byng | Statement: [John Byng, familyName, Byng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Byng Context triple: [John Byng, familyName, Byng]
-
A.
Byng
chosen
Byng is an English surname most notably associated with Julian Byng, a British Army officer and World War I general who later served as Governor General of Canada.
-
B.
Beynes
Beynes is a commune in the Yvelines department of the Île-de-France region in north-central France.
-
C.
Brannan
Brannan is a surname of English and Irish origin borne by various notable individuals, including American politician Charles F. Brannan.
-
D.
Lundey
Lundey is a small, uninhabited island off the coast of Reykjavík, Iceland, best known as a nesting site for Atlantic puffins and other seabirds.
-
E.
Bordon
Bordon is a town in East Hampshire, England, historically known for its large army camp and military training facilities.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a85b9ac8190a57c1fdaeacbe3d6 |
completed | April 10, 2026, 5:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6e851a6688190996580a077496833 |
completed | April 21, 2026, 3 a.m. |
Created at: April 8, 2026, 9:37 p.m.