Triple
T13496784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German telephone numbering plan |
E320781
|
entity |
| Predicate | directoryEnquiryPrefixExample |
P43716
|
FINISHED |
| Object | 118xx |
—
|
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: 118xx | Statement: [German telephone numbering plan, directoryEnquiryPrefixExample, 118xx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directoryEnquiryPrefixExample Context triple: [German telephone numbering plan, directoryEnquiryPrefixExample, 118xx]
-
A.
namePrefix
Indicates that one entity is a prefix or leading part of another entity’s name.
-
B.
usesDirectory
Indicates that one entity makes use of or operates within a particular directory in a file system or organizational structure.
-
C.
cataloguePrefix
chosen
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
-
D.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
E.
repositoryDirectoryName
Indicates the name assigned to the directory in which a repository is stored or organized.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4e9ca4819083116890a65389f9 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.