Triple
T34004777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch telephone numbering plan |
E871928
|
entity |
| Predicate | directoryEnquiryPrefix |
P148678
|
FINISHED |
| Object | 18xx |
—
|
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: 18xx | Statement: [Dutch telephone numbering plan, directoryEnquiryPrefix, 18xx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directoryEnquiryPrefix Context triple: [Dutch telephone numbering plan, directoryEnquiryPrefix, 18xx]
-
A.
directoryEnquiryNumbersStartWith
chosen
Indicates that the directory enquiry phone numbers begin with a specified prefix or sequence of digits.
-
B.
directoryOrganization
Indicates that one entity is organized or structured as a directory for another entity, typically grouping or arranging related items or records.
-
C.
directoryEntryType
Indicates the specific kind or classification of a directory entry within a directory or file system.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
usesDirectory
Indicates that one entity makes use of or operates within a particular directory in a file system or organizational structure.
- 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_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 1:50 a.m.