Triple
T34004762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch telephone numbering plan |
E871928
|
entity |
| Predicate | includesNumberType |
—
|
GENERATED |
| Object | geographic numbers |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesNumberType Context triple: [Dutch telephone numbering plan, includesNumberType, geographic numbers]
-
A.
hasNumberType
chosen
Indicates that an entity is associated with a specific category or type of number (such as integer, float, or identifier format).
-
B.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
C.
numericType
Indicates that one entity specifies or constrains the kind or category of numeric value associated with another entity.
-
D.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
E.
singsNumberType
Indicates that an entity performs singing characterized by a specific type or category of number (e.g., musical number or song type).
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 1, 2026, 1:50 a.m.