Triple
T34004781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch telephone numbering plan |
E871928
|
entity |
| Predicate | m2mPrefix |
P7142
|
FINISHED |
| Object | 097 |
—
|
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: 097 | Statement: [Dutch telephone numbering plan, m2mPrefix, 097]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: m2mPrefix Context triple: [Dutch telephone numbering plan, m2mPrefix, 097]
-
A.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
B.
tagPrefix
Indicates that one tag string serves as the starting substring (prefix) of another tag string in a tagging or labeling context.
-
C.
regionPrefix
Indicates that one region’s identifier or code serves as the starting substring (prefix) of another region’s identifier or code, expressing a hierarchical or nested regional relationship.
-
D.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
E.
registrationPrefix
chosen
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
- 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_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.