Triple
T4740475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2 road |
E105226
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Chatham |
E252130
|
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: Chatham | Statement: [A2 road, passesThrough, Chatham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chatham Context triple: [A2 road, passesThrough, Chatham]
-
A.
Chatham
Chatham is a coastal town on the southeastern tip of Cape Cod in Massachusetts, known for its beaches, historic lighthouse, and maritime character.
-
B.
Chatham
chosen
Chatham is a historic town in Kent, England, best known for its former Royal Navy dockyard and maritime heritage.
-
C.
Chatham
Chatham is a residential neighborhood on Chicago’s South Side known for its historic African American middle-class community and strong local institutions.
-
D.
Fairhaven
Fairhaven is a historic coastal town in southeastern Massachusetts known for its picturesque harbor, rich maritime heritage, and well-preserved 19th-century architecture.
-
E.
Newhaven
Newhaven is a historic coastal district of Edinburgh, Scotland, known for its former fishing village, harbor, and maritime heritage.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be43ab20848190879de3a0d6366523 |
completed | March 21, 2026, 7:07 a.m. |
Created at: March 20, 2026, 1:19 p.m.