Triple
T9831391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Much Hoole |
E238991
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | PRESTON |
E24766
|
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: PRESTON | Statement: [Much Hoole, hasPostTown, PRESTON]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PRESTON Context triple: [Much Hoole, hasPostTown, PRESTON]
-
A.
East Preston
East Preston is a coastal village in West Sussex, England, situated within the Arun District and known for its residential character and seaside location.
-
B.
Preston
Preston is a residential area and suburb within the Metropolitan Borough of North Tyneside in North East England.
-
C.
Preston
chosen
Preston is a historic industrial city in Lancashire, England, known for its role in the Industrial Revolution and its status as a major urban center in the North West.
-
D.
Preston
Preston is a masculine given name of English origin that has been used both as a first name and a surname.
-
E.
Preston
Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3297bd88190bf8c53a4ba00e0ae |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1d5c066a08190baabf3141c10d9f3 |
completed | April 5, 2026, 3:23 a.m. |
Created at: March 30, 2026, 8:32 p.m.