Triple
T13496769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German telephone numbering plan |
E320781
|
entity |
| Predicate | usesOpenNumberingPlan |
P110647
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [German telephone numbering plan, usesOpenNumberingPlan, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOpenNumberingPlan Context triple: [German telephone numbering plan, usesOpenNumberingPlan, true]
-
A.
telephoneNumberingPlan
Indicates a relationship where a telephone numbering plan defines or governs how telephone numbers are structured, assigned, or managed for a given telecommunication context.
-
B.
supportsNumberPorting
Indicates that an entity enables or allows the transfer of an existing phone number from one service or provider to another.
-
C.
serviceNumbering
Indicates that a specific service is assigned or associated with a particular identifying number or code.
-
D.
telephoneNumberingScope
Indicates the range or domain within which a particular telephone number or numbering plan is valid, managed, or applicable.
-
E.
usesHarmonizedNumberingWith
Indicates that two entities apply the same standardized numbering scheme so their identifiers or codes are directly comparable or aligned.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.