Triple
T36031274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth West |
E1042264
|
entity |
| Predicate | hasPostcodePreviously |
P200137
|
FINISHED |
| Object | 5113 |
—
|
LITERAL 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: 5113 | Statement: [Elizabeth West, hasPostcodePreviously, 5113]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostcodePreviously Context triple: [Elizabeth West, hasPostcodePreviously, 5113]
-
A.
hasPostalHistory
Indicates that an entity possesses or is associated with a record of its past postal or mailing activities.
-
B.
hasPostcodeAreaNow
Indicates that an entity is currently located within, or associated with, a specific postcode area.
-
C.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
D.
hasFormerAddress
Indicates that an entity was previously located at or associated with a particular address, but no longer is.
-
E.
hadPostOffice
Indicates that a place or entity possessed or was served by an official post office facility.
- F. None of above. chosen
Provenance (4 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
| PDg | Predicate description generation | batch_69ff76ab9b4c8190b4cc7c9c733b2765 |
completed | May 9, 2026, 6:02 p.m. |
Created at: May 3, 2026, 4:07 p.m.