Triple
T7543081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peg Maltby |
E178328
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Maltby |
E178328
|
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: Maltby | Statement: [Peg Maltby, hasSurname, Maltby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maltby Context triple: [Peg Maltby, hasSurname, Maltby]
-
A.
Maltby
chosen
Maltby is an English surname of likely locational origin, associated with various places named Maltby in England.
-
B.
Maltby, North Yorkshire
Maltby, North Yorkshire is a small village and civil parish in the Borough of Stockton-on-Tees in North Yorkshire, England.
-
C.
Maltby, South Yorkshire
Maltby, South Yorkshire is a former coal mining town and civil parish in the Metropolitan Borough of Rotherham in South Yorkshire, England.
-
D.
Mobberley
Mobberley is a rural village and civil parish in Cheshire, England, known for its historic church, traditional pubs, and proximity to Manchester Airport.
-
E.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8762b048190a0b262f9cb3fe1b0 |
completed | March 27, 2026, 9:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c86834713481908400504fb7b49068 |
completed | March 28, 2026, 11:45 p.m. |
Created at: March 27, 2026, 3:48 p.m.