Triple
T15815269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge, Ontario |
E383457
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object |
Preston
Preston is a historic community and former town that now serves as one of the main neighbourhoods within the city of Cambridge, Ontario.
|
E1178344
|
NE FINISHED |
How this triple was built (4 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: [Cambridge, Ontario, hasNeighbourhood, Preston]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Preston Context triple: [Cambridge, Ontario, hasNeighbourhood, Preston]
-
A.
Preston
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.
-
B.
Preston
Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
-
C.
Preston
Preston is a suburb in Melbourne, Australia, served by its own railway station on the metropolitan train network.
-
D.
Preston
Preston is a village in East Lothian, Scotland, known historically for its association with the nearby town of Prestonpans and its role in the region’s agricultural and industrial development.
-
E.
Preston
Preston is a masculine given name of English origin that has been used both as a first name and a surname.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Preston Triple: [Cambridge, Ontario, hasNeighbourhood, Preston]
Generated description
Preston is a historic community and former town that now serves as one of the main neighbourhoods within the city of Cambridge, Ontario.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Preston Target entity description: Preston is a historic community and former town that now serves as one of the main neighbourhoods within the city of Cambridge, Ontario.
-
A.
Preston
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.
-
B.
Preston
Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
-
C.
Preston
Preston is a residential area and suburb within the Metropolitan Borough of North Tyneside in North East England.
-
D.
Preston
Preston is a village in East Lothian, Scotland, known historically for its association with the nearby town of Prestonpans and its role in the region’s agricultural and industrial development.
-
E.
Preston
Preston is a suburb in Melbourne, Australia, served by its own railway station on the metropolitan train network.
- F. None of above. chosen
Provenance (5 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a219508190b8588120ec415ac7 |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff99959f048190ae24a072387ec233 |
completed | May 9, 2026, 8:31 p.m. |
| NEDg | Description generation | batch_69ff9ad6b29081909ff2abb2c4d866a4 |
completed | May 9, 2026, 8:36 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff9b443280819088dbf18f7c57406b |
completed | May 9, 2026, 8:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.