Triple
T20670733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ML3 |
E508014
|
entity |
| Predicate | addressingSystem |
P1216
|
FINISHED |
| Object | UK postcode system |
—
|
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: UK postcode system | Statement: [ML3, addressingSystem, UK postcode system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressingSystem Context triple: [ML3, addressingSystem, UK postcode system]
-
A.
usesAddressingSystem
chosen
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
B.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
C.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
D.
addressComponents
Indicates how an address is broken down into its constituent parts or fields (such as street, city, state, and postal code) and how those parts relate to the overall address.
-
E.
hasStreetNumberingSystem
Indicates that a location or area uses an organized system for assigning numbers to buildings or addresses along its streets.
- F. None of above.
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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c735048190a01cb7692928d66e |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.