Triple
T34549752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Código Postal de México |
E887028
|
entity |
| Predicate | hasOnlineLookup |
P108407
|
FINISHED |
| Object | postal code search on Correos de México website |
—
|
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: postal code search on Correos de México website | Statement: [Código Postal de México, hasOnlineLookup, postal code search on Correos de México website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineLookup Context triple: [Código Postal de México, hasOnlineLookup, postal code search on Correos de México website]
-
A.
hasOnlineCoverage
Indicates that an entity is covered, reported on, or featured in online media or digital publications.
-
B.
isAvailableOnline
chosen
Indicates that something can be accessed or obtained via the internet.
-
C.
hasOnlineRequirement
Indicates that an entity must be accessed, completed, or fulfilled through an online or internet-based component.
-
D.
hasOnlineProvision
Indicates that an entity offers or supports a service, feature, or function through an online or internet-based channel.
-
E.
hasOnlineForecastService
Indicates that an entity provides an online service through which users can access forecasts.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.