Triple
T4879809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godstone |
E109295
|
entity |
| Predicate | postTown |
P2711
|
FINISHED |
| Object | GODSTONE |
E109295
|
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: GODSTONE | Statement: [Godstone, postTown, GODSTONE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GODSTONE Context triple: [Godstone, postTown, GODSTONE]
-
A.
Godstone
chosen
Godstone is a village in Surrey, England, known for its historic charm and location near major transport routes.
-
B.
Elfstone
Elfstone is an honorific name given to Aragorn, the Dúnedain ranger who becomes King Elessar in J.R.R. Tolkien’s Middle-earth legendarium.
-
C.
Balderstone
Balderstone is a district and residential area within the Balderstone and Kirkholt ward of Rochdale in Greater Manchester, England.
-
D.
Ingatestone
Ingatestone is a historic village and civil parish in southeast England known for its traditional architecture and commuter links to London.
-
E.
Stonar
Stonar is a locality in the South Thanet area of Kent, England, historically associated with the former port of Sandwich and nearby coastal developments.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6803a1c081908972984241276c19 |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:27 p.m.