Triple
T11214730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Rushworth Jellicoe |
E265406
|
entity |
| Predicate | middleName |
P143
|
FINISHED |
| Object | Rushworth |
E45132
|
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: Rushworth | Statement: [John Rushworth Jellicoe, middleName, Rushworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rushworth Context triple: [John Rushworth Jellicoe, middleName, Rushworth]
-
A.
Rushworth
Rushworth is a small rural town in northern Victoria, Australia, known for its gold rush heritage and historic streetscape.
-
B.
Rushworth
chosen
Rushworth is the middle name of Lord Jellicoe, a British naval officer and statesman who served as First Sea Lord during World War I.
-
C.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
D.
Ruskington
Ruskington is a large village and civil parish in Lincolnshire, England, known for its rural character and position near the River Slea.
-
E.
Ruxley
Ruxley is a locality in the London Borough of Bromley, England, known for its mix of suburban development and nearby nature reserves such as the Ruxley Gravel Pits.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8e8eef48190932a85784ce15c86 |
completed | April 9, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4ad135154819091026334d25cd287 |
completed | April 19, 2026, 10:23 a.m. |
Created at: April 8, 2026, 9:30 p.m.