Triple
T9682488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindsay Reade |
E234317
|
entity |
| Predicate | basedIn |
P40
|
FINISHED |
| Object | Manchester |
E114
|
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: Manchester | Statement: [Lindsay Reade, basedIn, Manchester]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Manchester Context triple: [Lindsay Reade, basedIn, Manchester]
-
A.
Manchester
chosen
Manchester is a major city in northwest England known for its industrial heritage, vibrant cultural scene, and influential contributions to music, sport, and science.
-
B.
Manchester
Manchester is the most populous city in the U.S. state of New Hampshire and a major economic and cultural center for the region.
-
C.
Manchester
Manchester is a historic neighborhood on Pittsburgh’s North Side known for its 19th-century architecture and designation as a historic district.
-
D.
Manchester
Manchester is a suburban town in central Connecticut known for its historic mills, shopping districts, and residential communities within the Greater Hartford area.
-
E.
York
York is a common English surname historically associated with the city of York in England and borne by various notable individuals and families.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ccdbcc48190a4a9a70b3f419ac2 |
completed | April 1, 2026, 10:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1af759b8081909cfa41fc32196623 |
completed | April 5, 2026, 12:40 a.m. |
Created at: March 30, 2026, 8:16 p.m.