Triple
T1496326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford, Surrey |
E29694
|
entity |
| Predicate | postcodeArea |
P920
|
FINISHED |
| Object | TW |
E140097
|
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: TW | Statement: [Ashford, Surrey, postcodeArea, TW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TW Context triple: [Ashford, Surrey, postcodeArea, TW]
-
A.
TW
TW is the two-letter ISO 3166 country code assigned to Taiwan (commonly referred to as Chinese Taipei in certain international contexts).
-
B.
TW
chosen
TW is a UK postcode area in southwest London and parts of Surrey, covering towns such as Twickenham and Staines-upon-Thames.
-
C.
TR
TR is the two-letter ISO 3166-1 alpha-2 country code assigned to Turkey for international standardization and referencing.
-
D.
TOR
TOR is the standard three-letter abbreviation used to represent the Toronto Maple Leafs in sports standings, statistics, and media.
-
E.
TH
TH is the two-letter ISO 3166-1 alpha-2 country code assigned to Thailand for international standardization and identification.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6ec70c48190a94f6e1002848eae |
completed | March 1, 2026, 11:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad1cadb50481908788b5710f6012db |
completed | March 8, 2026, 6:52 a.m. |
Created at: March 1, 2026, 8:12 p.m.