Triple
T34004780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch telephone numbering plan |
E871928
|
entity |
| Predicate | mobilePrefix |
P110648
|
FINISHED |
| Object | 06 |
—
|
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: 06 | Statement: [Dutch telephone numbering plan, mobilePrefix, 06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilePrefix Context triple: [Dutch telephone numbering plan, mobilePrefix, 06]
-
A.
mobilePrefixExample
chosen
Indicates that the subject is an example or sample instance of a mobile phone number prefix associated with the object.
-
B.
mobileNumbersHaveNoGeographicAreaCode
Indicates that mobile phone numbers are not associated with or constrained by any specific geographic area code.
-
C.
mobileNumbersDistinguishedBy
Indicates that multiple mobile phone numbers are differentiated from one another based on some distinguishing attribute or criterion.
-
D.
nationalPrefixForDomesticCalls
Indicates the dialing prefix that must be used when making domestic telephone calls within a given country or numbering plan.
-
E.
associatedCountryCodePrefix
Indicates that one entity has a country code prefix that is associated with, or corresponds to, the other entity.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.