Triple
T34004783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch telephone numbering plan |
E871928
|
entity |
| Predicate | localSubscriberNumberLength |
P178144
|
FINISHED |
| Object | 7 digits |
—
|
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: 7 digits | Statement: [Dutch telephone numbering plan, localSubscriberNumberLength, 7 digits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localSubscriberNumberLength Context triple: [Dutch telephone numbering plan, localSubscriberNumberLength, 7 digits]
-
A.
subscriberNumberLengthRange
Indicates the allowed minimum and maximum length range for a subscriber’s phone number in a given context.
-
B.
usesVariableLengthSubscriberNumbers
Indicates that the system or service employs subscriber numbers whose lengths can vary rather than being fixed.
-
C.
mobileNumberLength
chosen
Indicates the required or actual number of digits in a mobile phone number associated with an entity.
-
D.
areaCodeLength
Indicates the number of digits or characters that make up a given area code.
-
E.
maximumNationalNumberLength
Indicates the greatest number of digits allowed in a national (domestic) phone number for a given country or numbering plan.
- 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_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:50 a.m.