Triple

T34004757
Position Surface form Disambiguated ID Type / Status
Subject Dutch telephone numbering plan E871928 entity
Predicate minimumNumberLength P26954 FINISHED
Object 9 digits including 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: 9 digits including trunk prefix | Statement: [Dutch telephone numbering plan, minimumNumberLength, 9 digits including trunk prefix]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: minimumNumberLength
Context triple: [Dutch telephone numbering plan, minimumNumberLength, 9 digits including trunk prefix]
  • A. minimumNumber chosen
    Indicates that the associated value is the smallest or least quantity allowed, required, or observed within a given set or context.
  • B. minimumSize
    Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
  • C. minimumTerm
    Indicates the shortest or least duration, period, or term that must apply within a given relationship or agreement.
  • D. minimumTrackLength
    Indicates the smallest allowable or observed length that a track must have within a given context or system.
  • E. minimumWidth
    Indicates that there is a specified smallest allowable or required width for something in the relationship.
  • 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_69f71362f1448190985a80ce7af475cb completed May 3, 2026, 9:20 a.m.
PD Predicate disambiguation batch_69f7127884388190884f23d181a65d19 completed May 3, 2026, 9:16 a.m.
Created at: May 1, 2026, 1:50 a.m.