Triple
T14471503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambourn |
E358852
|
entity |
| Predicate | postalTown |
P2711
|
FINISHED |
| Object | Hungerford |
E42529
|
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: Hungerford | Statement: [Lambourn, postalTown, Hungerford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hungerford Context triple: [Lambourn, postalTown, Hungerford]
-
A.
Hungerford
chosen
Hungerford is a historic market town and civil parish in West Berkshire, England, situated on the River Kennet and the Kennet and Avon Canal.
-
B.
Hensel
Hensel is a German surname most notably associated with mathematician Kurt Hensel, known for introducing p-adic numbers.
-
C.
Gamelin
Gamelin is a French surname most notably associated with General Maurice Gamelin, the commander-in-chief of the French Army at the start of World War II.
-
D.
Hartshorne
Hartshorne is a village in South Derbyshire, England, known for its rural character and historic parish church.
-
E.
Hurwitz
Hurwitz is a surname of German and Ashkenazi Jewish origin borne by various notable individuals across fields such as mathematics, music, and law.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f969788190a5114f92d7159aae |
completed | April 14, 2026, 7:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d8ae5508190aea1cab0b059f804 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:20 a.m.