Triple
T34004782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch telephone numbering plan |
E871928
|
entity |
| Predicate | geographicAreaCodeLength |
P110642
|
FINISHED |
| Object | 2 to 3 digits after trunk prefix |
—
|
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: 2 to 3 digits after trunk prefix | Statement: [Dutch telephone numbering plan, geographicAreaCodeLength, 2 to 3 digits after trunk prefix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicAreaCodeLength Context triple: [Dutch telephone numbering plan, geographicAreaCodeLength, 2 to 3 digits after trunk prefix]
-
A.
areaCodeLength
Indicates the number of digits or characters that make up a given area code.
-
B.
countryCodeLength
Indicates the number of characters that a given country code consists of.
-
C.
hasAreaCodeCountry
Indicates that a particular telephone area code is associated with or belongs to a specific country.
-
D.
usesVariableLengthAreaCodes
chosen
Indicates that the telephone numbering plan in question employs area codes whose lengths are not fixed but can vary.
-
E.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
- 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_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:50 a.m.