Triple
T16954211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord George Howe |
E411254
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Howe |
E34373
|
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: Howe | Statement: [Lord George Howe, familyName, Howe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Howe Context triple: [Lord George Howe, familyName, Howe]
-
A.
Howe
chosen
Howe is an English-language surname of Anglo-Norman and Old English origin, borne by numerous notable figures across politics, the military, the arts, and sports.
-
B.
Leahey
Leahey is a surname variant of Leahy, an Irish family name of Gaelic origin.
-
C.
Frontenacs
Frontenacs is the commonly used name for the Kingston Frontenacs, a major junior ice hockey team in the Ontario Hockey League based in Kingston, Ontario.
-
D.
Hayes
Hayes is a common English surname borne by numerous notable figures in politics, entertainment, sports, and other fields.
-
E.
Hayes
Hayes is a suburban town in west London, England, known for its residential areas, transport links, and proximity to Heathrow Airport.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01b04e88190a72735541b3bb117 |
completed | April 18, 2026, 6:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d464762c8190a734ffdd83633f70 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.