Triple
T8583981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orton Waterville |
E203254
|
entity |
| Predicate | hasPostcodeArea |
P920
|
FINISHED |
| Object | PE |
E229875
|
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: PE | Statement: [Orton Waterville, hasPostcodeArea, PE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PE Context triple: [Orton Waterville, hasPostcodeArea, PE]
-
A.
PE
chosen
PE is a postcode area in eastern England covering parts of Cambridgeshire, Lincolnshire, Norfolk, and surrounding counties.
-
B.
PE
PE is the official vehicle registration code for the Brazilian state of Pernambuco.
-
C.
PE
PE is the two-letter ISO 3166-1 alpha-2 country code assigned to Peru for international standardization and referencing.
-
D.
PE
PE is the official two-letter postal abbreviation used for Prince Edward Island, a Canadian province.
-
E.
Pe
Pe is a Hebrew consonant letter that represents a "p" or "f" sound and has both standard and final written forms.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbeb1ecc188190bbe2ab8d2423505b |
completed | March 31, 2026, 3:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce89bfb95c81909660460d5813fdaf |
completed | April 2, 2026, 3:22 p.m. |
Created at: March 30, 2026, 6:22 p.m.