Triple
T2346018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Rushworth Jellicoe |
E45132
|
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
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.
-
B.
Highworth
Highworth is a historic market town in Wiltshire, England, known for its elevated position and traditional architecture.
-
C.
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.
-
D.
Ashtead
Ashtead is a large suburban village in Surrey, England, known for its residential character, local amenities, and proximity to the town of Leatherhead.
-
E.
Rustington
Rustington is a large coastal village and civil parish on the English Channel in the Arun District of West Sussex, England.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6c7cb9481909405aeb503f804ae |
completed | March 7, 2026, 6:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aef0913e748190bbb5c54b86b415bd |
completed | March 9, 2026, 4:08 p.m. |
Created at: March 4, 2026, 7:52 p.m.