Triple
T10695629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham |
E252130
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Strood |
E212148
|
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: Strood | Statement: [Chatham, hasNeighbour, Strood]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Strood Context triple: [Chatham, hasNeighbour, Strood]
-
A.
Strood
chosen
Strood is a town in the unitary authority of Medway in Kent, England, situated on the River Medway opposite Rochester and forming part of the Medway Towns conurbation.
-
B.
Strood Green
Strood Green is a residential neighbourhood within the town of Strood in Medway, South East England.
-
C.
Wetstraat
Wetstraat is a major thoroughfare in Brussels that serves as a central hub for Belgian federal institutions and key European Union buildings.
-
D.
Strandvliet
Strandvliet is a metro station in Amsterdam that serves passengers on the city's rapid transit network.
-
E.
Cromstrijen
Cromstrijen was a former municipality in the Dutch province of South Holland, comprising several villages on the island of Hoeksche Waard.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd3af5248190ab807965255e9ad2 |
completed | April 9, 2026, 1:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d998da1738819099a9090c3e8badc9 |
completed | April 11, 2026, 12:42 a.m. |
Created at: April 8, 2026, 9:11 p.m.